Vehicle battery assembly systems and methods

ABSTRACT

Techniques are disclosed for systems and methods to provide modular battery assemblies for micro-mobility fleet vehicles. A modular battery assembly for a micro-mobility fleet vehicle includes a battery assembly enclosure including an assembly retention interface configured to physically secure the assembly enclosure to a subframe assembly of the micro-mobility fleet vehicle, a battery cell assembly disposed within the battery assembly enclosure, and an enclosure lid mounted to the assembly enclosure. The modular battery assembly may include an arched floorboard panel configured to provide a floor board surface for the micro-mobility fleet vehicle. The battery cell assembly may include a honeycomb battery cell holder and a collector board atop the battery cell holder to provide wire bond interconnects between the battery cells.

TECHNICAL FIELD

One or more embodiments of the present disclosure relate generally topowering electric vehicles and more particularly, for example, tosystems and methods for providing modular battery assemblies forelectric vehicles.

BACKGROUND

Contemporary transportation services may incorporate a variety ofdifferent types of vehicles, including motorized or electric kickscooters, bicycles, and/or motor scooters generally designed totransport one or two people at once (collectively, micro-mobility fleetvehicles). While micro-mobility fleet vehicles provide an additionaldimension of transportation flexibility, particularly when such vehiclesare incorporated into a dynamic transportation matching system thatlinks requestors or riders to fleet vehicles for hire or temporaryrental and personal use, such flexibility is only realizable if asignificant portion of the fleet is ready for operation and/orindividual nonoperational fleet vehicles can be quickly serviced andmade operational. As such, servicing a relatively extensive fleet ofmicro-mobility fleet vehicles can present a significant and cumbersomebut necessary capital investment and labor (e.g., time and cost) burdento a fleet manager/servicer.

Therefore, there is a need in the art for systems and methods to reducefleet servicer burdens associated with servicing micro-mobility fleetvehicles, particularly in the context of a dynamic transportationmatching system providing transportation services incorporating suchmicro-mobility fleet vehicles.

SUMMARY

Techniques are disclosed for systems and methods to provide modularbattery assemblies for micro-mobility fleet vehicles. In accordance withone or more embodiments, a modular battery assembly for a micro-mobilityfleet vehicle may include a rectangular cuboid shaped battery assemblyenclosure comprising an enclosure cavity, a battery assembly electricalinterface, a head assembly retention interface disposed along a frontportion of the battery assembly enclosure, and a tail assembly retentioninterface disposed along a rear portion of the battery assemblyenclosure, wherein the head and tail assembly retention interfaces areconfigured to physically secure the assembly enclosure to a subframeassembly mounted to the micro-mobility fleet vehicle; a battery cellassembly disposed within the enclosure cavity and electrically coupledto the battery assembly electrical interface of the battery assemblyenclosure; an enclosure lid mounted to the assembly enclosure andconfigured to seal the enclosure cavity and to prevent ambient moisturefrom entering the battery assembly enclosure; and an arched floorboardpanel disposed along a top portion of the enclosure lid and configuredto provide a floorboard surface for the micro-mobility fleet vehicle,wherein the arched floorboard panel and the battery assembly enclosureare configured to distribute a step weight of a rider of themicro-mobility fleet vehicle along the subframe assembly mounted to themicro-mobility fleet vehicle

In additional embodiments, a method for replacing a modular batteryassembly for a micro-mobility fleet vehicle may include receiving arelease request for a first modular battery assembly coupled to amicro-mobility fleet vehicle; releasing the first modular batteryassembly; and detecting installation of a second modular batteryassembly, wherein the first modular battery assembly comprises a batteryassembly enclosure comprising an enclosure cavity, a battery assemblyelectrical interface, and an assembly retention interface disposed alongthe battery assembly enclosure, wherein the assembly retention interfaceis configured to physically secure the assembly enclosure to a subframeassembly mounted to the micro-mobility fleet vehicle; a battery cellassembly disposed within the enclosure cavity and electrically coupledto the battery assembly electrical interface; an enclosure lid mountedto the assembly enclosure and configured to seal the enclosure cavityand to prevent ambient moisture from entering the battery assemblyenclosure; and an arched floorboard panel disposed along a top portionof the enclosure lid and configured to provide a floorboard surface forthe micro-mobility fleet vehicle.

According to some embodiments, a non-transitory machine-readable mediummay include a plurality of machine-readable instructions which whenexecuted by one or more processors are adapted to cause the one or moreprocessors to perform a method. In some embodiments, the method mayinclude receiving a release request for a first modular battery assemblycoupled to a micro-mobility fleet vehicle; releasing the first modularbattery assembly; and detecting installation of a second modular batteryassembly, wherein the first modular battery assembly comprises a batteryassembly enclosure comprising an enclosure cavity, a battery assemblyelectrical interface, and an assembly retention interface disposed alongthe battery assembly enclosure, wherein the assembly retention interfaceis configured to physically secure the assembly enclosure to a subframeassembly mounted to the micro-mobility fleet vehicle; a battery cellassembly disposed within the enclosure cavity and electrically coupledto the battery assembly electrical interface; an enclosure lid mountedto the assembly enclosure and configured to seal the enclosure cavityand to prevent ambient moisture from entering the battery assemblyenclosure; and an arched floorboard panel disposed along a top portionof the enclosure lid and configured to provide a floorboard surface forthe micro-mobility fleet vehicle.

In accordance with one or more additional embodiments, a modular batteryassembly for a micro-mobility fleet vehicle may include a batteryassembly enclosure comprising an enclosure cavity and a battery assemblyelectrical interface; a battery cell assembly comprising a plurality ofbattery cells disposed within the enclosure cavity and electricallycoupled to the battery assembly electrical interface of the batteryassembly enclosure; and an enclosure lid mounted to the assemblyenclosure and configured to seal the enclosure cavity and to preventambient moisture from entering the battery assembly enclosure. Thebattery cell assembly may include honeycomb battery cell holdercomprising a hexagonally packed array of hexagonal prism shaped batterycell cavities extending along a full length of each one of the pluralityof battery cells enclosed therein; and a collector board disposed atopthe honeycomb battery cell holder and including an array of battery cellaccess wells and board pads exposed at a top surface of the collectorboard and configured to provide physical access to each battery cellsufficient to wire bond each positive terminal and negative terminal ofeach battery cell to a corresponding board pad.

In additional embodiments, a method for replacing a modular batteryassembly for a micro-mobility fleet vehicle may include receiving arelease request for a first modular battery assembly coupled to amicro-mobility fleet vehicle; releasing the first modular batteryassembly; and detecting installation of a second modular batteryassembly, wherein the first modular battery assembly comprises a batteryassembly enclosure comprising an enclosure cavity and a battery assemblyelectrical interface; a battery cell assembly comprising a plurality ofbattery cells disposed within the enclosure cavity and electricallycoupled to the battery assembly electrical interface of the batteryassembly enclosure; and an enclosure lid mounted to the assemblyenclosure and configured to seal the enclosure cavity and to preventambient moisture from entering the battery assembly enclosure. Thebattery cell assembly may include a honeycomb battery cell holdercomprising a hexagonally packed array of hexagonal prism shaped batterycell cavities extending along a full length of each one of the pluralityof battery cells enclosed therein.

According to some embodiments, a non-transitory machine-readable mediummay include a plurality of machine-readable instructions which whenexecuted by one or more processors are adapted to cause the one or moreprocessors to perform a method. In some embodiments, the method mayinclude receiving a release request for a first modular battery assemblycoupled to a micro-mobility fleet vehicle; releasing the first modularbattery assembly; and detecting installation of a second modular batteryassembly, wherein the first modular battery assembly comprises a batteryassembly enclosure comprising an enclosure cavity and a battery assemblyelectrical interface; a battery cell assembly comprising a plurality ofbattery cells disposed within the enclosure cavity and electricallycoupled to the battery assembly electrical interface of the batteryassembly enclosure; and an enclosure lid mounted to the assemblyenclosure and configured to seal the enclosure cavity and to preventambient moisture from entering the battery assembly enclosure. Thebattery cell assembly may include a honeycomb battery cell holdercomprising a hexagonally packed array of hexagonal prism shaped batterycell cavities extending along a full length of each one of the pluralityof battery cells enclosed therein.

The scope of the invention is defined by the claims, which areincorporated into this section by reference. A more completeunderstanding of embodiments of the invention will be afforded to thoseskilled in the art, as well as a realization of additional advantagesthereof, by a consideration of the following detailed description of oneor more embodiments. Reference will be made to the appended sheets ofdrawings that will first be described briefly.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram of a portion of a dynamictransportation matching system including a fleet vehicle in accordancewith an embodiment of the disclosure.

FIG. 2 illustrates a block diagram of a dynamic transportation matchingsystem incorporating a variety of transportation modalities inaccordance with embodiments of the disclosure.

FIGS. 3A-D illustrate diagrams of micro-mobility fleet vehicles for usein a dynamic transportation matching system in accordance withembodiments of the disclosure.

FIG. 4A illustrates a block circuit diagram of a propulsion controlsystem for a micro-mobility fleet vehicle in accordance with anembodiment of the disclosure.

FIG. 4B illustrates a block data flow diagram of a propulsion controlsystem for a micro-mobility fleet vehicle in accordance with anembodiment of the disclosure.

FIG. 4C illustrates a block circuit diagram of a modular batteryassembly for a micro-mobility fleet vehicle in accordance with anembodiment of the disclosure.

FIG. 4D illustrates a diagram of a micro-mobility fleet vehicleincluding a modular battery assembly in accordance with an embodiment ofthe disclosure.

FIGS. 5A-B illustrate various aspects of a modular battery assembly fora micro-mobility fleet vehicle in accordance with embodiments of thedisclosure.

FIGS. 6A-J illustrate various aspects of a modular battery assembly fora micro-mobility fleet vehicle in accordance with embodiments of thedisclosure.

FIGS. 7A-E illustrate various aspects of a modular battery assembly fora micro-mobility fleet vehicle in accordance with embodiments of thedisclosure.

FIGS. 8A-D illustrate various aspects of a modular battery assembly fora micro-mobility fleet vehicle in accordance with embodiments of thedisclosure.

FIGS. 9A-B illustrate various aspects of a modular battery assembly fora micro-mobility fleet vehicle in accordance with embodiments of thedisclosure.

FIG. 10 illustrates a flow diagram of a process to replace (e.g., removeand/or install) a modular battery assembly for a micro-mobility fleetvehicle in accordance with an embodiment of the disclosure.

Embodiments of the invention and their advantages are best understood byreferring to the detailed description that follows. It should beappreciated that like reference numerals are used to identify likeelements illustrated in one or more of the figures.

DETAILED DESCRIPTION

In accordance with various embodiments of the present disclosure,modular battery assemblies for micro-mobility fleet vehicles and relatedmethodologies are provided to reduce burdens associated with servicingmicro-mobility fleet vehicles (e.g., electric kick scooters, bicycles,motor scooters, and/or other vehicles generally designed to transportone or two people at once). For example, a modular battery assembly mayinclude assembly retention interfaces configured to physically securethe modular battery assembly to a subframe assembly that can be mountedto a number of different micro-mobility fleet vehicles and/or differenttypes of micro-mobility fleet vehicles, such that manufacturingefficiencies can be realized for overall reduced capital investmentexpenditures related to maintaining an operational fleet of suchvehicles. Moreover, the assembly retention interfaces and correspondingretention mechanisms (e.g., integrated with the subframe assembly),along with other characteristics of the modular battery assembly, may bedesigned and/or configured to increase ease of battery replacement(e.g., removal and/or installation) for micro-mobility fleet vehicles,thereby reducing costs involved in the labor used to service eachmicro-mobility fleet vehicle.

In some embodiments, a modular battery assembly may include structuralelements to allow the modular battery assembly to form a weight bearingportion (e.g., a floorboard surface) of the micro-mobility fleetvehicle, which may be shaped and/or designed to ease battery replacementand reduce overall weight by eliminating a need for separate structuralelements of the micro-mobility fleet vehicle to provide the weightbearing portion, as described herein. In various embodiments, a modularbattery assembly may include logic devices and/or memory or data storagedevices and/or interfaces configured to monitor, store, and reportbattery monitoring data (e.g., number and depth of charge cycles,temperature profiles, cell status, estimated charge capacity, powerdelivery characteristics, and/or other battery monitoring data), forexample, and/or to receive vehicle status data (e.g., location, usagestatistics, power utilization efficiency statistics, other sensor data,other vehicle status data) and monitor, store, and report such receivedvehicle status data, such as to a field servicer while charging, asdescribed herein. In a particular embodiment, such logic and/or memoryor data storage devices/interfaces may be configured to receive firmwareand/or other fleet servicer distribution data while charging, forexample, and to provide such fleet servicer distribution data tocomponents of a micro-mobility fleet vehicle upon installation into themicro-mobility fleet vehicle, so as to reduce resource utilization(e.g., communication, labor, and other technological and/orinfrastructural resources) that would otherwise be necessary inproviding similar servicing of micro-mobility fleet vehicles,particularly when the micro-mobility fleet vehicles form part of adynamic transportation matching system, as described herein.

FIG. 1 illustrates a block diagram of a portion of a dynamictransportation matching system (e.g., system 100) including a fleetvehicle 110 in accordance with an embodiment of the disclosure. In theembodiment shown in FIG. 1 , system 100 includes fleet vehicle 110 andoptional user device 130. In general, fleet vehicle 110 may be apassenger vehicle designed to transport a single user (e.g., amicro-mobility fleet vehicle) or a group of people (e.g., a typical caror truck). More specifically, fleet vehicle 110 may be implemented as amotorized or electric kick scooter, bicycle, and/or motor scooterdesigned to transport one or perhaps two people at once typically on apaved road (collectively, micro-mobility fleet vehicles), as a typicalautomobile configured to transport up to 4, 7, or 10 people at once, oraccording to a variety of different transportation modalities (e.g.,transportation mechanisms). Fleet vehicles similar to fleet vehicle 110may be owned, managed, and/or serviced primarily by a fleetmanager/servicer providing fleet vehicle 110 for rental and use by thepublic as one or more types of transportation modalities offered by adynamic transportation matching system, for example, or may be owned,managed, and/or serviced by a private owner using the dynamictransportation matching system to match their vehicle to atransportation request, such as with ridesharing or ridesourcingapplications typically executed on a mobile user device, such as userdevice 130 as described herein. Optional user device 130 may be asmartphone, tablet, near field communication (NFC) or radio-frequencyidentification (RFID) enabled smart card, or other personal or portablecomputing and/or communication device that may be used to facilitaterental and/or operation of fleet vehicle 110.

As shown in FIG. 1 , fleet vehicle 110 may include one or more of acontroller 112, a user interface 113, an orientation sensor 114, agyroscope/accelerometer 116, a global navigation satellite systemreceiver (GNSS) 118, a wireless communications module 120, a camera 148,a propulsion system 122, an air quality sensor 150, and other modules126. Operation of fleet vehicle 110 may be substantially manual,autonomous, and/or partially or completely controlled by optional userdevice 130, which may include one or more of a user interface 132, awireless communications module 134, a camera 138, and other modules 136.In other embodiments, fleet vehicle 110 may include any one or more ofthe elements of user device 130. In some embodiments, one or more of theelements of system 100 may be implemented in a combined housing orstructure that can be coupled to or within fleet vehicle 110 and/or heldor carried by a user of system 100.

Controller 112 may be implemented as any appropriate logic device (e.g.,processing device, microcontroller, processor, application specificintegrated circuit (ASIC), field programmable gate array (FPGA), memoryor data storage device, memory reader, or other device or combinationsof devices) that may be adapted to execute, store, and/or receiveappropriate instructions, such as software instructions implementing acontrol loop for controlling various operations of fleet vehicle 110and/or other elements of system 100, for example. Such softwareinstructions may also implement methods for processing images and/orother sensor signals or data, determining sensor information, providinguser feedback (e.g., through user interface 113 or 132), queryingdevices for operational parameters, selecting operational parameters fordevices, or performing any of the various operations described herein(e.g., operations performed by logic devices of various devices ofsystem 100).

In addition, a non-transitory medium may be provided for storing machinereadable instructions for loading into and execution by controller 112.In these and other embodiments, controller 112 may be implemented withother components where appropriate, such as volatile memory,non-volatile memory, one or more interfaces, and/or various analogand/or digital components for interfacing with devices of system 100.For example, controller 112 may be adapted to store sensor signals,sensor information, parameters for coordinate frame transformations,calibration parameters, sets of calibration points, and/or otheroperational parameters, over time, for example, and provide such storeddata to a user via user interface 113 or 132. In some embodiments,controller 112 may be integrated with one or more other elements offleet vehicle 110, for example, or distributed as multiple logic deviceswithin fleet vehicle 110 and/or user device 130.

In some embodiments, controller 112 may be configured to substantiallycontinuously monitor and/or store the status of and/or sensor dataprovided by one or more elements of fleet vehicle 110 and/or user device130, such as the position and/or orientation of fleet vehicle 110 and/oruser device 130, for example, and the status of a communication linkestablished between fleet vehicle 110 and/or user device 130. Suchcommunication links may be established and then provide for transmissionof data between elements of system 100 substantially continuouslythroughout operation of system 100, where such data includes varioustypes of sensor data, control parameters, and/or other data.

User interface 113 of fleet vehicle 110 may be implemented as one ormore of a display, a touch screen, a keyboard, a mouse, a joystick, aknob, a steering wheel, a yoke, and/or any other device capable ofaccepting user input and/or providing feedback to a user. In variousembodiments, user interface 113 may be adapted to provide user input(e.g., as a type of signal and/or sensor information transmitted bywireless communications module 134 of user device 130) to other devicesof system 100, such as controller 112. User interface 113 may also beimplemented with one or more logic devices (e.g., similar to controller112) that may be adapted to store and/or execute instructions, such assoftware instructions, implementing any of the various processes and/ormethods described herein. For example, user interface 132 may be adaptedto form communication links, transmit and/or receive communications(e.g., infrared images and/or other sensor signals, control signals,sensor information, user input, and/or other information), for example,or to perform various other processes and/or methods described herein.

In one embodiment, user interface 113 may be adapted to display a timeseries of various sensor information and/or other parameters as part ofor overlaid on a graph or map, which may be referenced to a positionand/or orientation of fleet vehicle 110 and/or other elements of system100. For example, user interface 113 may be adapted to display a timeseries of positions, headings, and/or orientations of fleet vehicle 110and/or other elements of system 100 overlaid on a geographical map,which may include one or more graphs indicating a corresponding timeseries of actuator control signals, sensor information, and/or othersensor and/or control signals. In some embodiments, user interface 113may be adapted to accept user input including a user-defined targetheading, waypoint, route, and/or orientation, for example, and togenerate control signals to cause fleet vehicle 110 to move according tothe target heading, route, and/or orientation. In other embodiments,user interface 113 may be adapted to accept user input modifying acontrol loop parameter of controller 112, for example.

Orientation sensor 114 may be implemented as one or more of a compass,float, accelerometer, and/or other device capable of measuring anorientation of fleet vehicle 110 (e.g., magnitude and direction of roll,pitch, and/or yaw, relative to one or more reference orientations suchas gravity and/or Magnetic North), camera 148, and/or other elements ofsystem 100, and providing such measurements as sensor signals and/ordata that may be communicated to various devices of system 100.Gyroscope/accelerometer 116 may be implemented as one or more electronicsextants, semiconductor devices, integrated chips, accelerometersensors, accelerometer sensor systems, or other devices capable ofmeasuring angular velocities/accelerations and/or linear accelerations(e.g., direction and magnitude) of fleet vehicle 110 and/or otherelements of system 100 and providing such measurements as sensor signalsand/or data that may be communicated to other devices of system 100(e.g., user interface 132, controller 112).

GNSS receiver 118 may be implemented according to any global navigationsatellite system, including a GPS, GLONASS, and/or Galileo basedreceiver and/or other device capable of determining absolute and/orrelative position of fleet vehicle 110 (e.g., or an element of fleetvehicle 110) based on wireless signals received from space-born and/orterrestrial sources (e.g., eLoran, and/or other at least partiallyterrestrial systems), for example, and capable of providing suchmeasurements as sensor signals and/or data (e.g., coordinates) that maybe communicated to various devices of system 100. In some embodiments,GNSS 118 may include an altimeter, for example, or may be used toprovide an absolute altitude.

Wireless communications module 120 may be implemented as any wirelesscommunications module configured to transmit and receive analog and/ordigital signals between elements of system 100. For example, wirelesscommunications module 120 may be configured to receive control signalsand/or data from user device 130 and provide them to controller 112and/or propulsion system 122. In other embodiments, wirelesscommunications module 120 may be configured to receive images and/orother sensor information (e.g., still images or video images) and relaythe sensor data to controller 112 and/or user device 130. In someembodiments, wireless communications module 120 may be configured tosupport spread spectrum transmissions, for example, and/or multiplesimultaneous communications channels between elements of system 100.Wireless communication links formed by wireless communications module120 may include one or more analog and/or digital radio communicationlinks, such as WiFi, Bluetooth, NFC, RFID, and others, as describedherein, and may be direct communication links established betweenelements of system 100, for example, or may be relayed through one ormore wireless relay stations configured to receive and retransmitwireless communications. In various embodiments, wireless communicationsmodule 120 may be configured to support wireless mesh networking, asdescribed herein.

In some embodiments, wireless communications module 120 may beconfigured to be physically coupled to fleet vehicle 110 and to monitorthe status of a communication link established between fleet vehicle 110and/or user device 130. Such status information may be provided tocontroller 112, for example, or transmitted to other elements of system100 for monitoring, storage, or further processing, as described herein.In addition, wireless communications module 120 may be configured todetermine a range to another device, such as based on time of flight,and provide such range to the other device and/or controller 112.Communication links established by communication module 120 may beconfigured to transmit data between elements of system 100 substantiallycontinuously throughout operation of system 100, where such dataincludes various types of sensor data, control parameters, and/or otherdata, as described herein.

Propulsion system 122 may be implemented as one or more motor-basedpropulsion systems, and/or other types of propulsion systems that can beused to provide motive force to fleet vehicle 110 and/or to steer fleetvehicle 110. In some embodiments, propulsion system 122 may includeelements that can be controlled (e.g., by controller 112 and/or userinterface 113) to provide motion for fleet vehicle 110 and to provide anorientation for fleet vehicle 110. In various embodiments, propulsionsystem 122 may be implemented with a portable power supply, such as abattery and/or a combustion engine/generator and fuel supply.

For example, in some embodiments, such as when propulsion system 122 isimplemented by an electric motor (e.g., as with many micro-mobilityfleet vehicles), fleet vehicle 110 may include battery 124. Battery 124may be implemented by one or more battery cells (e.g., lithium ionbattery cells) and be configured to provide electrical power topropulsion system 122 to propel fleet vehicle 110, for example, as wellas to various other elements of system 100, including controller 112,user interface 113, and/or wireless communications module 120. In someembodiments, battery 123 may be implemented with its own safetymeasures, such as thermal interlocks and a fire-resistant enclosure, forexample, and may include one or more logic devices, sensors, and/or adisplay to monitor and provide visual feedback of a charge status ofbattery 124 (e.g., a charge percentage, a low charge indicator, etc.).

Other modules 126 may include other and/or additional sensors,actuators, communications modules/nodes, and/or user interface devices,for example, and may be used to provide additional environmentalinformation related to operation of fleet vehicle 110, for example. Insome embodiments, other modules 126 may include a humidity sensor, awind and/or water temperature sensor, a barometer, an altimeter, a radarsystem, a proximity sensor, a visible spectrum camera or infrared camera(with an additional mount), and/or other environmental sensors providingmeasurements and/or other sensor signals that can be displayed to a userand/or used by other devices of system 100 (e.g., controller 112) toprovide operational control of fleet vehicle 110 and/or system 100. Infurther embodiments, other modules 126 may include a light, such as aheadlight or indicator light, and/or an audible alarm, both of which maybe activated to alert passersby to possible theft, abandonment, and/orother critical statuses of fleet vehicle 110. In particular, and asshown in FIG. 1 , other modules 126 may include camera 148 and/or airquality sensor 150.

Camera 148 may be implemented as an imaging device including an imagingmodule including an array of detector elements that can be arranged in afocal plane array. In various embodiments, camera 148 may include one ormore logic devices (e.g., similar to controller 112) that can beconfigured to process imagery captured by detector elements of camera148 before providing the imagery to communications module 120. Moregenerally, camera 148 may be configured to perform any of the operationsor methods described herein, at least in part, or in combination withcontroller 112 and/or user interface 113 or 132.

In various embodiments, air quality sensor 150 may be implemented as anair sampling sensor configured to determine an air quality of anenvironment about fleet vehicle 110 and provide corresponding airquality sensor data. Air quality sensor data provided by air qualitysensor 150 may include particulate count, methane content, ozonecontent, and/or other air quality sensor data associated with commonstreet level sensitivities and/or health monitoring typical when in astreet level environment, such as that experienced when riding on atypical micro-mobility fleet vehicle, as described herein.

Fleet vehicles implemented as micro-mobility fleet vehicles may includea variety of additional features designed to facilitate fleet managementand user and environmental safety. For example, as shown in FIG. 1 ,fleet vehicle 110 may include one or more of docking mechanism 140,operator safety measures 142, vehicle security device 144, and/or userstorage 146, as described in more detail herein.

In particular, in some embodiments, operator safety measures 142 may beimplemented as one or more of a headlight, a taillight, ambientlighting, a programmable lighting element (e.g., a multi-color panel,strip, or array of individual light elements, such as addressable lightemitting diodes (LEDs), recessed and/or directional lighting, actuatedlighting (e.g., articulated lighting coupled to an actuator), and/orother lighting coupled to and/or associated with fleet vehicle 110 andcontrolled by controller 112. In other embodiments, operator safetymeasures 142 may include a speaker or other audio element configured togenerate an audible alarm or sound to warn a rider or passersby of adetected safety concern, for example, or to inform a rider of apotential safety concern. More generally, operator safety measures 142may be any electronic, mechanical, or electromechanical device orsubsystem configured to increase the safety of a rider and/or mitigatepotential harm to a rider under nominal operating conditions.

User interface 132 of user device 130 may be implemented as one or moreof a display, a touch screen, a keyboard, a mouse, a joystick, a knob, asteering wheel, a yoke, and/or any other device capable of acceptinguser input and/or providing feedback to a user. In various embodiments,user interface 132 may be adapted to provide user input (e.g., as a typeof signal and/or sensor information transmitted by wirelesscommunications module 134 of user device 130) to other devices of system100, such as controller 112. User interface 132 may also be implementedwith one or more logic devices (e.g., similar to controller 112) thatmay be adapted to store and/or execute instructions, such as softwareinstructions, implementing any of the various processes and/or methodsdescribed herein. For example, user interface 132 may be adapted to formcommunication links, transmit and/or receive communications (e.g.,infrared images and/or other sensor signals, control signals, sensorinformation, user input, and/or other information), for example, or toperform various other processes and/or methods described herein.

In one embodiment, user interface 132 may be adapted to display a timeseries of various sensor information and/or other parameters as part ofor overlaid on a graph or map, which may be referenced to a positionand/or orientation of fleet vehicle 110 and/or other elements of system100. For example, user interface 132 may be adapted to display a timeseries of positions, headings, and/or orientations of fleet vehicle 110and/or other elements of system 100 overlaid on a geographical map,which may include one or more graphs indicating a corresponding timeseries of actuator control signals, sensor information, and/or othersensor and/or control signals. In some embodiments, user interface 132may be adapted to accept user input including a user-defined targetheading, waypoint, route, and/or orientation, for example, and togenerate control signals to cause fleet vehicle 110 to move according tothe target heading, route, and/or orientation. In other embodiments,user interface 132 may be adapted to accept user input modifying acontrol loop parameter of controller 112, for example.

Wireless communications module 134 may be implemented as any wirelesscommunications module configured to transmit and receive analog and/ordigital signals between elements of system 100. For example, wirelesscommunications module 134 may be configured to transmit control signalsfrom user interface 132 to wireless communications module 120 or 144. Insome embodiments, wireless communications module 134 may be configuredto support spread spectrum transmissions, for example, and/or multiplesimultaneous communications channels between elements of system 100. Invarious embodiments, wireless communications module 134 may beconfigured to monitor the status of a communication link establishedbetween user device 130 and/or fleet vehicle 110 (e.g., including packetloss of transmitted and received data between elements of system 100,such as with digital communication links), and/or determine a range toanother device, as described herein. Such status information may beprovided to user interface 132, for example, or transmitted to otherelements of system 100 for monitoring, storage, or further processing,as described herein. In various embodiments, wireless communicationsmodule 134 may be configured to support wireless mesh networking, asdescribed herein.

Other modules 136 of user device 130 may include other and/or additionalsensors, actuators, communications modules/nodes, and/or user interfacedevices used to provide additional environmental information associatedwith user device 130, for example. In some embodiments, other modules136 may include a humidity sensor, a wind and/or water temperaturesensor, a barometer, a radar system, a visible spectrum camera, aninfrared camera, a GNSS receiver, and/or other environmental sensorsproviding measurements and/or other sensor signals that can be displayedto a user and/or used by other devices of system 100 (e.g., controller112) to provide operational control of fleet vehicle 110 and/or system100 or to process sensor data to compensate for environmentalconditions. As shown in FIG. 1 , other modules 136 may include camera138.

Camera 138 may be implemented as an imaging device including an imagingmodule including an array of detector elements that can be arranged in afocal plane array. In various embodiments, camera 138 may include one ormore logic devices (e.g., similar to controller 112) that can beconfigured to process imagery captured by detector elements of camera138 before providing the imagery to communications module 120. Moregenerally, camera 138 may be configured to perform any of the operationsor methods described herein, at least in part, or in combination withcontroller 138 and/or user interface 113 or 132.

In general, each of the elements of system 100 may be implemented withany appropriate logic device (e.g., processing device, microcontroller,processor, application specific integrated circuit (ASIC), fieldprogrammable gate array (FPGA), memory or data storage device, memoryreader, or other device or combinations of devices) that may be adaptedto execute, store, and/or receive appropriate instructions, such assoftware instructions implementing a method for providing sensor dataand/or imagery, for example, or for transmitting and/or receivingcommunications, such as sensor signals, sensor information, and/orcontrol signals, between one or more devices of system 100.

In addition, one or more non-transitory mediums may be provided forstoring machine readable instructions for loading into and execution byany logic device implemented with one or more of the devices of system100. In these and other embodiments, the logic devices may beimplemented with other components where appropriate, such as volatilememory, non-volatile memory, and/or one or more interfaces (e.g.,inter-integrated circuit (I2C) interfaces, mobile industry processorinterfaces (MIPI), joint test action group (JTAG) interfaces (e.g., IEEE1149.1 standard test access port and boundary-scan architecture), and/orother interfaces, such as an interface for one or more antennas, or aninterface for a particular type of sensor).

Sensor signals, control signals, and other signals may be communicatedamong elements of system 100 and/or elements of other systems similar tosystem 100 using a variety of wired and/or wireless communicationtechniques, including voltage signaling, Ethernet, WiFi, Bluetooth,Zigbee, Xbee, Micronet, Near-field Communication (NFC) or other mediumand/or short range wired and/or wireless networking protocols and/orimplementations, for example. In such embodiments, each element ofsystem 100 may include one or more modules supporting wired, wireless,and/or a combination of wired and wireless communication techniques,including wireless mesh networking techniques. In some embodiments,various elements or portions of elements of system 100 may be integratedwith each other, for example, or may be integrated onto a single printedcircuit board (PCB) to reduce system complexity, manufacturing costs,power requirements, coordinate frame errors, and/or timing errorsbetween the various sensor measurements.

Each element of system 100 may include one or more batteries,capacitors, or other electrical power storage devices, for example, andmay include one or more solar cell modules or other electrical powergenerating devices. In some embodiments, one or more of the devices maybe powered by a power source for fleet vehicle 110, using one or morepower leads. Such power leads may also be used to support one or morecommunication techniques between elements of system 100.

FIG. 2 illustrates a block diagram of dynamic transportation matchingsystem 200 incorporating a variety of transportation modalities inaccordance with an embodiment of the disclosure. For example, as shownin FIG. 2 , dynamic transportation matching system 200 may includemultiple embodiments of system 100. In the embodiment shown in FIG. 2 ,dynamic transportation matching system 200 includes managementsystem/server 240 in communication with a number of fleet vehicles 110a-d and user devices 130 a-b over a combination of a typical wide areanetwork (WAN) 250, WAN communication links 252 (solid lines), a varietyof mesh network communication links 254 (curved dashed lines), and NFC,RFID, and/or other local communication links 256 (curved solid lines).Dynamic transportation matching system 200 also includes publictransportation status system 242 in communication with a variety ofpublic transportation vehicles, including one or more buses 210 a,trains 210 b, and/or other public transportation modalities, such asships, ferries, light rail, subways, streetcars, trolleys, cable cars,monorails, tramways, and aircraft. As shown in FIG. 2 , all fleetvehicles are able to communicate directly to WAN 250 and, in someembodiments, may be able to communicate across mesh networkcommunication links 254, to convey fleet data and/or fleet status dataamongst themselves and/or to and from management system 240.

In FIG. 2 , a requestor may use user device 130 a to hire or rent one offleet vehicles 110 a-d by transmitting a transportation request tomanagement system 240 over WAN 250, allowing management system 240 topoll status of fleet vehicles 110 a-d and to select one of fleetvehicles 110 a-d to fulfill the transportation request; receiving afulfillment notice from management system 240 and/or from the selectedfleet vehicle, and receiving navigation instructions to proceed to orotherwise meet with the selected fleet vehicle. A similar process may beused by a requestor using user device 130 b, but where the requestor isable to enable a fleet vehicle over local communication link 263, asshown.

Management system 240 may be implemented as a server with controllers,user interfaces, communications modules, and/or other elements similarto those described with respect to system 100 of FIG. 1 , but withsufficient processing and storage resources to manage operation ofdynamic transportation matching system 200, including monitoringstatuses of fleet vehicles 110 a-d, as described herein. In someembodiments, management system 240 may be implemented in a distributedfashion and include multiple separate server embodiments linkedcommunicatively to each other direction and/or through WAN 250. WAN 250may include one or more of the Internet, a cellular network, and/orother wired or wireless WANs. WAN communication links 252 may be wiredor wireless WAN communication links, and mesh network communicationlinks 254 may be wireless communication links between and among fleetvehicles 110 a-d, as described herein.

User device 130 a in FIG. 2 includes a display of user interface 132that shows a planned route for a user attempting to travel fromorigination point 260 to destination 272 using different transportationmodalities (e.g., a planned multimodal route), as depicted inroute/street map 286 rendered by user interface 132. For example,management system 240 may be configured to monitor statuses of allavailable transportation modalities (e.g., including fleet vehicles andpublic transportation vehicles) and provide a planned multimodal routefrom origination point 260 to destination 272. Such planned multimodalroute may include, for example, walking route 262 from origination point260 to bus stop 264, bus route 266 from bus stop 264 to bus stop 268,and micro-mobility route 270 (e.g., using one of micro-mobility fleetvehicles 110 b, 110 c, or 110 d) from bus stop 268 to destination 272.Also shown rendered by user interface 132 are present location indicator280 (indicating a present absolute position of user device 130 a onstreet map 286), navigation destination selector/indicator 282 (e.g.,configured to allow a user to input a desired navigation destination),and notice window 284 (e.g., used to render fleet status data, includinguser notices and/or alerts, as described herein). For example, a usermay use navigation destination selector/indicator 282 to provide and/orchange destination 272, as well as change any leg or modality of themultimodal route from origination point 260 to destination 272. In someembodiments, notice window 284 may display instructions for traveling toa next waypoint along the determined multimodal route (e.g., directionsto walk to a bus stop, directions to ride a micro-mobility fleet vehicleto a next stop along the route, etc.).

In various embodiments, management system 240 may be configured toprovide or suggest an optimal multimodal route to a user (e.g.,initially and/or while traversing a particular planned route), and auser may select or make changes to such route through manipulation ofuser device 130 a, as shown. For example, management system 240 may beconfigured to suggest a quickest route, a least expensive route, a mostconvenient route (to minimize modality changes or physical actions auser must take along the route), an inclement weather route (e.g., thatkeeps the user protected from inclement weather a maximum amount of timeduring route traversal), or some combination of those that is determinedas best suited to the user, such as based on various user preferences.Such preferences may be based on prior use of system 200, prior usertrips, a desired arrival time and/or departure time (e.g., based on userinput or obtained through a user calendar or other data source), orspecifically input or set by a user for the specific route, for example,or in general. In one example, origination point 260 may be extremelycongested or otherwise hard to access by a ride-share fleet vehicle,which could prevent or significantly increase a wait time for the userand a total trip time to arrive at destination 272. In suchcircumstances, a planned multimodal route may include directing the userto walk and/or take a scooter/bike to an intermediate and less congestedlocation to meet a reserved ride-share vehicle, which would allow theuser to arrive at destination 272 quicker than if the ride-share vehiclewas forced to meet the user at origination point 260. It will beappreciated that numerous different transportation-relevant conditionsmay exist or dynamically appear or disappear along a planned route thatmay make it beneficial to use different modes of transportation toarrive at destination 272 efficiently, including changes in trafficcongestion and/or other transportation-relevant conditions that occurmid-route, such as an accident along the planned route. Under suchcircumstances, management system 240 may be configured to adjust amodality or portion of the planned route dynamically in order to avoidor otherwise compensate for the changed conditions while the route isbeing traversed.

FIGS. 3A-C illustrate diagrams of micro-mobility fleet vehicles 110 b,110 c, and 110 d, which may be integrated with mobile mesh networkprovisioning systems in accordance with an embodiment of the disclosure.For example, fleet vehicle 110 b of FIG. 3A may correspond to amotorized bicycle for hire that is integrated with the various elementsof system 100 and may be configured to participate in dynamictransportation matching system 200 of FIG. 2 . As shown, fleet vehicle110 b includes controller/user interface/wireless communications module112/113/120 (e.g., integrated with a rear fender of fleet vehicle 110b), propulsion system 122 configured to provide motive power to at leastone of the wheels (e.g., a rear wheel 322) of fleet vehicle 110 b,battery 124 for powering propulsion system 122 and/or other elements offleet vehicle 110 b, docking mechanism 140 (e.g., a spade lock assembly)for docking fleet vehicle 110 b at a docking station, user storage 146implemented as a handlebar basket, and vehicle security device (e.g., anembodiment of vehicle security device 144 of FIG. 1 ), which mayincorporate one or more of a locking cable 144 a, a pin 144 b coupled toa free end of locking cable 144 a, a pin latch/insertion point 144 c, aframe mount 144 d, and a cable/pin holster 144 e, as shown(collectively, vehicle security device 144). In some embodiments,controller/user interface/wireless communications module 112/113/120 mayalternatively be integrated on and/or within a handlebar enclosure 313,as shown.

In some embodiments, vehicle security device 144 may be implemented as awheel lock configured to immobilizing rear wheel 322 of fleet vehicle110 b, such as by engaging pin 144 b with spokes of rear wheel 322. Inthe embodiment shown in FIG. 3A, vehicle security device 144 may beimplemented as a cable lock configured to engage with a pin latch on adocking station, for example, or to wrap around and/or through a securepole, fence, or bicycle rack and engage with pin latch 144 c. In variousembodiments, vehicle security device 144 may be configured to immobilizefleet vehicle 110 b by default, thereby requiring a user to transmit ahire request to management system 240 (e.g., via user device 130) tohire fleet vehicle 110 b before attempting to use fleet vehicle 110 b.The hire request may identify fleet vehicle 110 b based on an identifier(e.g., a QR code, a barcode, a serial number, etc.) presented on fleetvehicle 110 b (e.g., such as by user interface 113 on a rear fender offleet vehicle 110 b). Once the hire request is approved (e.g., paymentis processed), management system 240 may transmit an unlock signal tofleet vehicle 110 b (e.g., via network 250). Upon receiving the unlocksignal, fleet vehicle 110 b (e.g., controller 112 of fleet vehicle 110b) may release vehicle security device 144 and unlock rear wheel 322 offleet vehicle 110 b.

Fleet vehicle 110 c of FIG. 3B may correspond to a motorized sit-scooterfor hire that is integrated with the various elements of system 100 andmay be configured to participate in dynamic transportation matchingsystem 200 of FIG. 2 . As shown in FIG. 3B, fleet vehicle 110 c includesmany of the same elements as those discussed with respect to fleetvehicle 110 b of FIG. 3A. For example, fleet vehicle 110 c may includeuser interface 113, propulsion system 122, battery 124,controller/wireless communications module/cockpit enclosure 112/120/312,user storage 146 (e.g., implemented as a storage recess), and operatorsafety measures 142 a and 142 b, which may be implemented as varioustypes of headlight assemblies, taillight assemblies, programmable lightelements/strips/spotlights, and/or reflective strips, as describedherein. As shown in FIG. 3B, fleet vehicle 110 c may also be implementedwith various other vehicle light assemblies to increase visibility, toprovide ambient lighting, and/or to provide lighted beaconing, asdescribed herein.

Fleet vehicle 110 d of FIG. 3C may correspond to a motorized stand orkick scooter for hire that is integrated with the various elements ofsystem 100 and may be configured to participate in dynamictransportation matching system 200 of FIG. 2 . As shown in FIG. 3C,fleet vehicle 110 d includes many of the same elements as thosediscussed with respect to fleet vehicle 110 b of FIG. 3A. For example,fleet vehicle 110 d may include user interface 113, propulsion system122, battery 124, controller/wireless communications module/cockpitenclosure 112/120/312, and operator safety measures 142, which may beimplemented as various types of programmable light strips and/orreflective strips, as shown.

FIG. 3D illustrates a docking station 300 for docking fleet vehicles(e.g., fleet vehicles 110 c, 110 e, and 110 g, etc.) in accordance withembodiments of the disclosure. As shown in FIG. 3D, docking station 300may include multiple bicycle docks, such as docks 302 a-e. For example,a single fleet vehicle (e.g., any one of electric bicycles 304 a-d) maydock in each of docks 302 a-e of docking station 300. Each of docks 302a-e may include a lock mechanism for receiving and locking dockingmechanism 140 of electric bicycles 304 a-d. In some embodiments, once afleet vehicle is docked in a bicycle dock, the dock may beelectronically and/or communicatively coupled to the fleet vehicle(e.g., to controllers and/or wireless communications modules integratedwithin cockpit enclosures 312 a-d of fleet vehicles 304 a-d) via acommunication link such that the fleet vehicle may be charged by thedock and the fleet vehicle and the dock may communicate with each othervia the communication link (e.g., similar to communications over mobilemesh network 260), as described herein.

For example, a requestor may use user device 130 a to reserve, rent,and/or hire a fleet vehicle docked to one of bicycle docks 302 a-e bytransmitting a reservation request to management system 240. Once thereservation request is processed, management system 240 may transmit anunlock signal to a docked fleet vehicle and/or one of docks 302 a-e vianetwork 250 and/or mobile mesh network 260. One of docks 302 a-e mayautomatically unlock an associated lock mechanism to release the fleetvehicle based, at least in part, on such unlock signal. In someembodiments, each of docks 302 a-e may be configured to charge batteries(e.g., batteries 324 a-c) of electric bicycles 304 a-d while electricbicycles 304 a-d are docked at docks 302 a-e. In some embodiments,docking station 300 may also be configured to transmit statusinformation associated with docking station 300 (e.g., a number of fleetvehicles docked at docking station 300, charge statuses of docked fleetvehicles, and/or other fleet status information) to management system240.

In various embodiments, each of micro-mobility fleet vehicles 110 b-dmay be implemented with a subframe assembly configured to receive amodular battery assembly configured to power each one of micro-mobilityfleet vehicles 110 b-d. As described herein, such modular batteryassembly may include various features designed to ease batteryreplacement, reduce overall vehicle weight, and provide additionalservice burden-reducing functionality configured to help form a reliableand robust propulsion system and/or propulsion control system formicro-mobility fleet vehicles.

FIG. 4A illustrates a block circuit diagram of a propulsion controlsystem 400 for a micro-mobility fleet vehicle in accordance with anembodiment of the disclosure. As shown in FIG. 4A, propulsion controlsystem 400 may include propulsion system 122 configured to providemotive power for general operation of a micro-mobility fleet vehicle(e.g. one of micro-mobility fleet vehicles 110 b-d) based on controldata provided by controller 112 and/or user interface 113 over databuses 411 and/or 413, which may in some embodiments be integrated withincockpit assembly 312. In various embodiments, propulsion system 122 mayinclude motor controller 420 coupled between electrical motor 422 (e.g.,via power bus 421 and data bus 423), modular battery assembly 424 (e.g.,via power bus 425 and data bus 427), brake resistor 426 (e.g., via powerbus 428 and sensor/data bus 429), and elements of cockpit assembly 312(e.g., via data bus 411).

Motor controller 420 may be configured to receive control data (e.g.,throttle position, brake position, brake pressure, and/or other controldata, which may be generated based on user input provided to userinterface 113 and/or sourced directly from a fleet manager/servicer viamanagement system 240) and provide power sourced from modular batteryassembly 424 to motor 422 (e.g., to control acceleration of amicro-mobility fleet vehicle), provide power sourced from motor 422 tomodular battery assembly 424 (e.g., for regeneration charging) and/orbrake resistor 426 (e.g., to control electrical braking of amicro-mobility fleet vehicle), and/or to otherwise control operation ofpropulsion control system 122 and/or mediate operation of propulsioncontrol system 400. Electrical motor 422 may be configured to providemotive power for a micro-mobility fleet vehicle (e.g., tractive power torear wheel 322 of micro-mobility fleet vehicle 110 b) and to providemotor monitoring data to motor controller 420, which may use suchmonitoring data to control operation of motor 422 and/or other elementsof propulsion system 122, for example, and/or provide such monitoringinformation over the various data buses for monitoring, storage, and/orreporting, as described herein. Brake resistor 426 may be configured toprovide braking power for a micro-mobility fleet vehicle (e.g., brakingpower extracted as electrical power generated by rear wheel 322 ofmicro-mobility fleet vehicle 110 b) and to provide brake resistormonitoring data and/or corresponding sensor signals to motor controller420, which may use such monitoring data to control operation of motor422 and/or other elements of propulsion system 122, for example, and/orprovide such monitoring information over the various data buses formonitoring, storage, and/or reporting.

Modular battery assembly 424 may be configured to provide electricalpower to various elements of a micro-mobility fleet vehicle (e.g.,elements of fleet vehicle 110 in FIG. 1 ) and to provide batterymonitoring data to motor controller 420, which may use such monitoringdata to control operation of motor 422, modular battery assembly 424,and/or other elements of propulsion system 122, for example, and/orprovide such monitoring information over the various data buses formonitoring, storage, and/or reporting, as described herein. In someembodiments, data bus 427 of modular battery assembly 424 may include orprovide a relatively low voltage bus voltage source configured to powerthe various data and/or sensor buses of propulsion system 122 and/orassociated with elements of fleet vehicle 110.

In various embodiments, modular battery assembly 424 may be integratedwith a memory or data storage interface and/or device, for example, andmay be configured to receive all available monitoring data and/orvehicle status data (e.g., over data bus 427) and monitor, store, and/orreport such data, such as to or via various elements of fleet vehicle110, as described herein. In general, power buses 421, 425, and 428 maybe implemented by relatively large gauge wiring harnesses coupledbetween modular battery assembly 424, motor controller 420, motor 422,and brake resistor 426, and data buses 411, 413, 423, 427, and 429 maybe implemented by relative small gauge wiring harnesses coupled betweenthe various elements of propulsion control system 400. In someembodiments, data and power buses may be integrated within a singlewiring harness. In related embodiments, the various data buses may beimplemented according to a distributed vehicle data bus, such as aController Area Network (CAN) bus. In other embodiments, any one orcombination of the various data buses may be implemented wirelessly,such as by employing embodiments of wireless communications module 120of FIG. 1 .

FIG. 4B illustrates a block data flow diagram for propulsion controlsystem 400 for a micro-mobility fleet vehicle in accordance with anembodiment of the disclosure. As shown in FIG. 4B, propulsion controlsystem 400 may implement vehicle data links 430 and 432, vehicle sensorand/or data links 434, and fleet data links 436 between the variouselements of propulsion control system 400. In a specific embodiment,vehicle data links 430 and 432 may be formed over a CAN bus, vehiclesensor and/or data links 434 may be formed over a physically separatesensor and/or data signaling bus, and fleet data links 436 may be formedover one or more wireless data communication links (e.g., via a mesh,LAN, WAN, cellular, and/or combination of networks) to management system240. In general, modular battery assembly 424 may be configured toprovide battery assembly monitoring data 437 to, and/or receivemonitoring and/or control data from, motor controller 420 and/orcontroller 112 over vehicle data links 430 and 432; controller 112 maybe configured to receive and provide propulsion system monitoring andcontrol data 431 among motor controller 420 and modular battery assembly424 over vehicle data links 430, for example, and to communicate suchmonitoring and control data with management system 240 via fleet datalinks 436; and user interface 113 may be configured to receive and/orprovide vehicle control data 433 over vehicle data links 430, as shown.

FIG. 4C illustrates a block circuit diagram of modular battery assembly424 for a micro-mobility fleet vehicle in accordance with an embodimentof the disclosure. As shown in FIG. 4C, modular battery assembly 424 mayinclude battery management system 442 configured to monitor batterycells 444 and control operation of modular battery assembly 424,including charging, discharging, balancing, and overvoltage protectionof battery cells 444; reporting proper installation of modular batteryassembly 424 into a receiving micro-mobility fleet vehicle and/orcharging station (e.g., an embodiment of docking station 300 of FIG.3D); powering and/or monitoring vehicle data bus 427; and/or logging(monitoring, storing, reporting) monitoring and/or control datacommunicated over data bus 427. For example, battery management system442 may be configured to provide control signals tometal-oxide-semiconductor field-effect transistor banks 450 and/or 451to discharge battery cells 444 and provide power over power bus 425 orto charge battery cells 444 and receive power over power bus 425; tocontrol operation of switch 452 to provide for a soft start of motor422; to detect an overvoltage condition or thermal excursion of batterycells 444 (via balance leads 448, monitoring leads 449, and/or othermonitoring leads within modular battery assembly 424) and openprogrammable fuse 454 to mitigate damage to battery cells 444 and/orother elements of modular battery assembly 424 and/or propulsion system122 otherwise caused by such overvoltage condition or thermal excursion;to monitor data bus 427 for control data directing operation of modularbattery assembly 424; to provide battery monitoring data over data bus427, which may include providing battery monitoring data and/or othervehicle data to system logger 446 for monitoring and/or storage tomemory/data storage device/interface 447, for example, or retrievingsuch stored data from memory 447 and/or system logger 446 for subsequentreporting over data bus 427. In some embodiments, battery managementsystem 442 may be configured to generate bus source voltage 427-1 fordata bus 427 (e.g., drawn from and/or DC to DC converted from powerprovided by battery cells 444), which may be distributed across all databusses and/or provided to any one or combination of elements ofpropulsion control system 400 and/or fleet vehicle 110.

In general, battery management system 442 and/or system logger 446 maybe implemented by any one or combination of logic devices, similar infunction and implementation to controller 112 and/or other elements offleet vehicle 110 of FIG. 1 . Memory 447 may be implemented as apermanent or removable data storage device, such as any readable,write-once, and/or rewriteable memory card. In some embodiments, batterymanagement system 442, system logger 446, memory 447, and/or otherelements of modular battery assembly 424 depicted in the circuit diagramof FIG. 4C, aside from battery cells 444, may be integrated into amonolithic printed circuit board (PCB), which may include multipletraces, interfaces, integrated circuits, and/or other devices selectedand coupled to each other to perform the functions described withrespect to the various elements of the circuit diagram depicted by FIG.4C.

Battery cells 444 may be implemented by a plurality of rechargeableelectrical power storage cells, for example, such as 21700-sizedlithium-based rechargeable battery cells. In some embodiments, batterycells 444 may include a single ended battery cell, where both thepositive and negative terminals are disposed at the same end of thebattery cell (e.g., a central cap terminal, and a perimeter shoulderterminal), as described herein. Shunt 455 may be implemented as a diodeto ensure current flows along power bus 425 only in a desire direction,for example, or may be implemented as any other shunt device or currentmonitoring device or component of such device.

FIG. 4D illustrates a diagram of a micro-mobility fleet vehicle 410(e.g., a sit-scooter) including elements of propulsion control system400 and including modular battery assembly 424 in accordance with anembodiment of the disclosure. As shown in FIG. 4D, micro-mobility fleetvehicle 410 may include modular battery assembly 424 coupled to asubframe assembly 462 of micro-mobility fleet vehicle 410. In theembodiment shown in FIG. 4D, subframe assembly 462 may be implemented asan aluminum subframe case disposed between and/or welded/coupled to lefttubular frame member 460 and right tubular frame member 461, such that along axis 480 of modular battery assembly 424 is substantially parallelto a longitudinal axis 403 of micro-mobility fleet vehicle 410 whenmodular battery assembly 424 is properly secured to subframe assembly462. Longitudinal axis 403 is parallel to the general direction oftravel in the frame of reference of micro-mobility fleet vehicle 410 andis perpendicular to a lateral axis 404 of micro-mobility fleet vehicle410 (e.g., which is parallel to the rotational axis of rear wheel 322)and to a vertical axis 405 of micro-mobility fleet vehicle 410 (e.g.,which is generally antiparallel to the gravitation vector whenmicro-mobility fleet vehicle 410 is driven upright on a level flatsurface).

In the embodiment depicted by FIG. 4D, left tubular frame member 460 andright tubular frame member 461 may extend substantially longitudinallybetween front wheel 323 or steering column/head tube 321 and rear wheel322 to form floorboard cavity 481, in which subframe assembly 462 isdisposed, and font deck cavity 482, which may include a front deck panor other structure disposed between tubular frame members 460 and 461configured to support and/or enclose other elements of propulsioncontrol system 122, including brake resistor 426 and/or battery assemblyretention mechanism 463. Floorboard cavity 481 and/or front deck cavity482 may also contain power buses 425 and 428, motor controller 420, andpower bus 421 between motor controller 420 and motor 422 (e.g., whichmay be integrated with rear wheel 322 as shown). In various embodiments,one or more of power buses 421, 425, and 428, motor controller 420,subframe assembly 462, battery assembly retention mechanism 463, and/orbrake resistor 426 may be mounted to and/or supported by subframeassembly 463, such as between subframe assembly 462 and one or bothtubular frame members 460 and 461. For example, as shown in the insetdiagram of power control system 400 b, subframe assembly 462 may beimplemented as a subframe case configured to receive and at leastpartially enclose modular battery assembly 424 and power bus 425extending between modular battery assembly 424 and motor controller 420mounted to a rear facing panel of subframe assembly 462, as shown. Insome embodiments, one or more of power buses 421, 425, and 428 and motorcontroller 420 may be mounted to or within (e.g., integrated with)modular battery assembly 424.

As described herein, cockpit assembly 312, which may include userinterface 113, may be electronically coupled to other elements ofpropulsion control system 400 via one or more data buses, including adata bus wire harness extending through head tube 321 and one or both oftubular frame members 460 and 461 to motor controller 420, for example.In various embodiments, such data bus wire harness may be at leastpartially integrated with a wire harness implementing any one of powerbuses 421, 425, and 428.

FIGS. 5A-B illustrate various aspects of a modular battery assembly 524for a micro-mobility fleet vehicle (e.g., micro-mobility fleet vehicle410) in accordance with embodiments of the disclosure. As shown in theexploded view of modular battery assembly 524 presented in FIG. 5A,modular battery assembly 524 may include a rectangular cuboid shapedbattery assembly enclosure 510 and an enclosure lid 518 configured toform a sealed housing for battery cell assembly 540. Battery assemblyenclosure 510 may be formed from a thermally conductive material, suchas aluminum or a thermally conductive/impregnated resin, for example,and may include enclosure cavity 517, interface mounting orifice 511,battery assembly retention interface 512 (e.g., a head or tail assemblyretention interface, depending on an orientation of an associatedsubframe assembly within micro-mobility fleet vehicle 410), and variousother features configured to help physically secure and/or seal batterycell assembly 540 within enclosure cavity 517, such as seal groove 515in enclosure lip 514, threaded fastener holes 516 formed throughenclosure lip 514, and positioning ribs 513 within enclosure cavity 517.Battery assembly electrical interface 525 (e.g., a hermetic power/databus interface) may be mounted within interface mounting orifice 511, forexample, and may support leads for power bus 425 and/or data bus 427,which may be integrated into a single wire harness/bus 527. In someembodiments, battery management system 422 may be housed within batteryassembly enclosure 510, such as between battery cell assembly 540 andinterface mounting orifice 511. Enclosure lid 518 may be formed from asimilar material, for example, and may include fastener through holes520 configured to allow fasteners (e.g., screws) to fasten enclosure lid518 to battery assembly enclosure 510 and compress lid seal 519 withinseal groove 515 to form a watertight seal about battery cell assembly540 within enclosure cavity 517.

In various embodiments, battery cell assembly 540 may include batterycell holder 530 and battery cells 444, where battery cell holder 530 isformed from a thermally insulating and/or flame resistant material andincludes a packed array of battery cell shaped cavities configured tosecure battery cells 444 (e.g., by press fit within each individual cellcavity) and provide a desired spacing and relative orientation betweeneach individual cell and its neighbors. In some embodiments, batterycell holder 530 may include various features configured to helpphysically secure battery cell assembly 540 within enclosure cavity 517,such as mating surfaces configured to mate with positioning ribs 513 ora bottom surface of enclosure cavity 517.

FIG. 5B presents an assembled view of modular battery assembly 524, withenclosure lid 518 fastened to and sealing battery cell assembly 540within enclosure cavity 517 (e.g., using fasteners threaded throughfastener through holes 520 and into threaded fastener holes 516 tocompress lid seal 519 within seal groove 515). In the embodiment shownin FIG. 5B, battery assembly retention interface 512 is implemented as ahinge receiver recess, and battery assembly retention interface 512 andbattery assembly electrical interface 525 may be configured to mate witha corresponding hinge guide to hinge into a secured position within asubframe assembly, as described more fully herein with respect to FIGS.7A-E.

FIGS. 6A-J illustrate various aspects of modular battery assembly 624for a micro-mobility fleet vehicle (e.g., micro-mobility fleet vehicle410) in accordance with embodiments of the disclosure. As shown in theexploded view of modular battery assembly 624 presented in FIG. 6A,modular battery assembly 624 may include a rectangular cuboid shapedbattery assembly enclosure 610 and an enclosure lid 618 configured toform a sealed housing for a battery cell assembly 640. Battery assemblyenclosure 610 may be formed from a thermally conductive material, suchas aluminum or a thermally conductive/impregnated resin, for example,and may include enclosure cavity 517, battery assembly retentioninterfaces 612 and/or 613 (e.g., head or tail assembly retentioninterfaces, depending on an orientation of an associated subframeassembly within micro-mobility fleet vehicle 410), assembly handle 617,battery assembly electrical interface 625, and various other featuresconfigured to help physically secure and/or seal battery cell assembly640 within enclosure cavity 517. Battery assembly electrical interface525 (e.g., a hermetic power/data bus interface) may be mounted to orthrough battery assembly enclosure 610, for example, and may supportleads for power bus 425 and/or data bus 427, which may be integratedinto a single wire harness/bus, as described herein.

In some embodiments, battery management system 422 may be housed withinbattery assembly enclosure 610, such as mounted to battery cell assembly640 between battery cell assembly 640 and battery assembly electricalinterface 625, for example, or may be mounted externally to batteryassembly enclosure 610, such as adjacent assembly handle 617 and/orassembly electrical interface 625. Enclosure lid 618 may be formed froma material similar to that used to form battery assembly enclosure 610,for example, and may include fastener through holes 620 configured toallow fasteners to fasten enclosure lid 618 to battery assemblyenclosure 610 and compress a lid seal or other sealing mechanism and/orform a watertight seal about battery cell assembly 640 within enclosurecavity 517.

In various embodiments, battery cell assembly 640 may include honeycombbattery cell holder 630, battery cells 444, collector board 650, andcell assembly lid 622. Honeycomb battery cell holder 630 may be formedfrom a thermally insulating and/or flame resistant material and includea hexagonally packed array of hexagonal prism shaped battery cellcavities extending along a full length of each battery cell 444 andconfigured to secure battery cells 444 (e.g., by press fit within eachindividual cell cavity) and provide a desired spacing and relativeorientation between each individual cell and its neighbors. In addition,battery cell holder 630 may include a collector board tray 631configured to support and/or position collector board 652 above batterycells 444 after they are press fit into honeycomb battery cell holder630. In some embodiments, battery cell holder 630 may include variousfeatures configured to help physically secure battery cell assembly 640within enclosure cavity 517, such as mating surfaces configured to matewith corresponding surfaces or a bottom surface of enclosure cavity 517,for example, or features configured to facilitate mounting of batterymanagement system 442 (e.g., in the form of a monolithic PCB) to batterycell holder 630, to facilitate securing collector board 650 to collectorboard tray 631, and/or to facilitate mounting cell assembly lid 622 tocollector board tray 631 and/or battery cell holder 630 over collectorboard 650.

Collector board 650 may be configured to interconnect each of batterycells 444 by wire bonding according to a desired output voltage, forexample, and to provide corresponding output power to battery managementsystem 442 (e.g., and power bus 425), such as through a highcurrent-capable board to board connector (e.g., a thick pinconnector/interface). As such, collector board 650 provides asignificant reduction in internal wiring and accompanying routingclutter. Each wire bond may be formed (e.g., using a selected thicknessof wire bond wire and/or wire bonding pressure, duration, and/or otherformation parameters) to act as an individual one-time fuse for eachbattery cell, such that if any cell attempts to pass too high a current(e.g., by shorting internally) and/or its terminals exceed apredetermined maximum operating temperature, the corresponding wirebond(s) will burn and/or open and isolate the faulty battery cell fromthe rest of battery cells 444.

In various embodiments, collector board 650 may be implemented as a PCBincluding a number of board pads exposed at a top surface of collectorboard 650 and interconnected by cell balance traces or lines extendingthrough and/or over collector board 650, an array of battery cell accessthrough holes or wells each configured to provide physical accessthrough collector board 650 to a top of an underlying battery cell thatis sufficient for wire bonding both terminals of the battery cell to anadjacent wire bonding pad, and a collector board electrical interface652 mounted at an edge of collector board 650 and electrically coupledto the wire bonding pads and/or the cell balance traces or linesextending through and/or over collector board 650. In some embodiments,collector board 650 may be mechanically secured to collector board tray631 of honeycomb battery cell holder 630 by heat staking and/oradhesive. Cell assembly lid 622 may be configured to snap into place tocollector board tray 631 over collector board 650 (e.g., secured byfeatures formed in cell assembly lid 622 and/or collector board tray631) in order to complete assembly of battery cell assembly 640 andprotect system assemblers and wire bonds associated with collector board650 and/or battery cells 444 from accidental contact.

As shown in FIG. 6A, modular battery assembly 624 may include an arrayof thermal adhesive disks 621 each configured to extend from a bottom ofenclosure cavity 517 through a similarly sized access hole at a bottomof a corresponding battery cell cavity of honeycomb battery cell holder630 to contact and thermally couple and/or mechanically secure eachbattery cell to battery assembly enclosure 610. In some embodiments,thermal adhesive disks 621 may be formed from a material that is able todeform to facilitate contacting and/or thermally coupling each batterycell to battery assembly enclosure 610, such as being extrudable throughthe access hole up to and about a base of the battery cell when batterycell assembly 640 is placed and/or pressed into enclosure cavity 517.

FIG. 6B presents a detailed top down view of an individual hexagonalprism shaped battery cell cavity 632 of honeycomb battery cell holder630. In FIG. 6B, the hexagonal perimeter of battery cell cavity 632forms six full length (e.g., cell length air gaps 633 that helpthermally isolate adjacent battery cells from each other and providespace for venting in the event of a thermal overrun of an individualcell. In some embodiments, battery cell cavity 632 may include one ormore crush ribs 634 disposed along a length of a surface of battery cellcavity 632, which may be configured to secure battery cell 444 in placebut allow insertion by press fit. In particular embodiments, batterycell cavity 632 may include one or more bottom vents 635 (e.g., notchesformed in corresponding bottom access holes) to allow a thermal adhesivedisk 621 to enter or extrude through the bottom access hole into thebottom of battery cell cavity 632 to contact a bottom of battery cell444 without being impeded by air pressure differentials, for example.

FIG. 6C presents a detailed orthographic view of battery cellsubassembly 640 c showing battery cells 444 press fit into battery cellcavities of honeycomb battery cell holder 630 so that a full length ofeach battery cell is encompassed by its corresponding battery cellcavity to provide increased thermal isolation properties, as describedherein. In FIG. 6C, honeycomb battery cell holder 630 includes fastenerholes 616, collector board tray 631, external alignment ribs 636 (e.g.to enclosure cavity 517), battery management system mounting features637, collector board alignment features 638, and positive electrode/cellcap 645 and negative electrode/cell shoulder 646 of battery cells 444,which may be selectively wire bonded to collector board 650, asdescribed herein.

FIG. 6D presents a detailed orthographic view of battery cellsubassembly 640 d showing collector board 650 secured to collector boardtray 631 of honeycomb battery cell holder 630 and wire bond pads 655 ofcollector board 650 wire bonded to select terminals of battery cells 444in honeycomb battery cell holder 630 to provide a desired output voltagefor modular battery assembly 624, as described herein. In the embodimentshown in FIG. 6D, collector board 650 includes a plurality of keyholeshaped cell access wells 654 arranged over corresponding battery cells444 in multiple parallel serial arrays 658 each including a series ofbattery cells 444 coupled serially (e.g., positive terminal to negativeterminal) by sections of wire bond wire 666 and cell cap wirebonds/welds 656, cell shoulder wire bonds/welds 657, and board pad wirebonds/welds 665 to board pads 655. As shown in FIG. 6D, some serialarrays (e.g., serial array 658) may include cell access wells 654oriented similarly across the length of the array, and other serialarrays (e.g., serial array 658) may include cell access wells 654oriented differently across the length of the array, such as to providefor physical clearance for collector board alignment features (e.g.,collector board alignment features 638 in FIG. 6C). In some embodiments,collector board 650 may include collector board electrical interface652, electrical interface 653 (e.g., a power bus interface or aninsertion detect interface), and/or a thermal sensor interface 651(e.g., sensor and/or data bus interface). For example, collector board650 may include a number of thermal sensors configured to providetemperature monitoring data associated with individual battery cellsand/or groups of battery cells, as described herein.

FIG. 6E presents a detailed top down view of battery cell subassembly640 d showing collector board 650 secured to collector board tray 631 ofhoneycomb battery cell holder 630 (e.g., via alignment features/headstakes 639) and an arrangement of wire bonds to select terminals ofbattery cells 444 through keyhole shaped cell access wells 654. In FIG.6E, keyhole shaped cell access wells 654 each include a disk portion 661configured to provide physical and/or wire bonding access to cell cap645 and a notch portion (e.g., displaced from disk portion 661 along along axis 660 of cell access well 654) configured to provide physicaland/or wire bonding access to cell shoulder 646. Wire bond wire sections666 can each be wire bonded to a cell cap 645, a board pad 655, and/or acell shoulder 646, as shown, such that the wire bonds carry the currentof constituent serial arrays (e.g., except at ends of the serial arrays,which may be coupled to power bus terminals/traces coupled to orembedded within collector board 650 and/or to collector board electricalinterfaces 652 and/or 653. Also shown in FIG. 6E are balance lines 663and 664, which may be coupled between board pads 655 and electricalinterface 652 and/or embedded within collector board 650. As describedherein, battery management system 442 may be configured to use balancelines 663 and 664 (e.g., similar to balance leads 448, monitoring leads449 of FIG. 4C) to balance serial arrays of battery cells (e.g., balancecharge among the various cell groups) of battery cell assembly 640.

FIG. 6F presents a detailed orthographic view of battery cellsubassembly 640 d showing collector board 650 secured to collector boardtray 631 of honeycomb battery cell holder 630 (e.g., via alignmentfeatures/head stakes 639) and an arrangement of wire bonds (e.g.,sections of wire bond wire 666, cell cap wire bonds/welds 656, cellshoulder wire bonds/welds 657, and board pad wire bonds/welds 665 toboard pads 655) to select terminals of battery cells 444 through a diskportion 661 of keyhole shaped cell access wells 654 and a notch portion662 displaced from the disk portion along long axis 660 of keyholeshaped cell access wells 654.

FIG. 6G presents a detailed orthographic view of battery cell assembly640 showing cell assembly lid 622 fitted to battery cell subassembly 640d of FIG. 6D, where cell assembly lid 622 includes access notches 623configured to align cell assembly lid 622 to honeycomb battery cellholder 630 and provide access to fastener holes 616, which may be usedto secure battery cell assembly 640 to battery assembly enclosure 610.FIG. 6H presents a detailed orthographic view of modular batterysubassembly 624 h showing thermal adhesive disks 621 arranged along abottom of enclosure cavity 517 to receive honeycomb battery cell holder630 of battery cell assembly 640 and thermally and mechanically couplebattery cells 444 embedded within battery cell holder 630 to batteryassembly enclosure 610. Also shown is enclosure lip 614 configured toform a seal with enclosure lid 618, as described herein. FIG. 6Ipresents a detailed orthographic view of modular battery assembly 624showing enclosure lid 618 coupled to battery assembly enclosure 610 toseal battery cell assembly 640 within the corresponding enclosure cavity517, as described herein. Also shown are fastener through holes 620 ofenclosure lid 618 configured to allow fasteners to fasten enclosure lid618 to battery assembly enclosure 610 and liquid-waterproof breathablepressure relief patch 611 configured to allow pressurized air and/orcontaminates to exit enclosure cavity 517 in the event of a cellrupture, thereby reducing the risk that pressure and contaminates causedby a cell rupture cause other battery cells in modular battery assembly624 to rupture. In various embodiments, pressure relief patch 611 may beimplemented, at least in part, by Gore-Tex fabric.

FIG. 6J presents a detailed cross section view of modular batteryassembly 624 showing enclosure lid 618 coupled to battery assemblyenclosure 610 to seal battery cell assembly 640 within the correspondingenclosure cavity 517, as described herein. Also shown in FIG. 6J arecell assembly lid 622 configured to provide head clearance 668 abovecollector board 650 for various wire bonds (e.g., board pad wire bonds665, call cap wire bonds 657) and facilitating relatively low pressureventing access in the event of a cell rupture, to help preventcollateral ruptures, as described herein. In addition, FIG. 6J showsenclosure gap 669 between honeycomb battery cell holder 630 and batteryassembly enclosure 610, which is also provided to help preventcollateral ruptures. As described herein, the hexagonal perimeter ofeach hexagonal prism shaped battery cell cavity 632 provides full lengthair gaps 633 about battery cells 444 for thermal isolation and ruptureventing purposes, and each battery cell cavity 632 includes a bottomaccess hole 639 allowing thermal adhesive disks 621 to contact andthermally couple a bottom of battery cell 444 to a bottom of batteryassembly enclosure 610, so as to help reduce risk of thermal excursionsin battery cells 444.

FIGS. 7A-E illustrate various aspects of a modular battery assembly 724for a micro-mobility fleet vehicle (e.g., micro-mobility fleet vehicle410) in accordance with embodiments of the disclosure. In particular,FIG. 7A shows three steps 702, 704, and 706 for installing modularbattery assembly 724 into a subframe assembly 762 implemented as asubframe case coupled between tubular frame members 460 and 461 andincluding a hinged head assembly retention mechanism 763 (e.g., a hingedassembly retention mechanism disposed towards head tube 321 and/or afront of micro-mobility fleet vehicle 410). In the embodiment shown inFIG. 7A, motor controller 430 is mounted to rear external face ofsubframe assembly 762, and subframe assembly 762 includes a floorpanpanel 774 providing a floorpan for micro-mobility fleet vehicle 410configured to protect modular battery assembly 724 from road debris.

In step 702, a fleet servicer technician may use ergonomic batteryassembly handle 717 to position modular battery assembly 724 over hingedassembly retention mechanism 763 with battery assembly retentioninterface 512 (e.g., a hinge receiver recess) generally spatiallyaligned with hinged assembly retention mechanism 763 (e.g., to alignwith a hinge guide and/or an electrical interface of hinged assemblyretention mechanism 763), such that arched floorboard panel 770 isfacing substantially towards head tube 321 and/or away from subframeassembly 762. In step 704, modular battery assembly 724 is lowered intohinged assembly retention mechanism 763 to mate battery assemblyretention interface 512 with hinged assembly retention mechanism 763. Instep 706, modular battery assembly 724 is pivoted into subframe assembly762 via hinged assembly retention mechanism 763 and secured in place bytail assembly retention mechanism 764 (e.g., an assembly retentionmechanism disposed towards rear wheel 322 and/or a rear ofmicro-mobility fleet vehicle 410). In alternative embodiments, a similarseries of steps may be used to install modular battery assembly 724 intoa subframe assembly implemented as a subframe case coupled betweentubular frame members 460 and 461 and including a hinged tail assemblyretention mechanism (e.g., a hinged assembly retention mechanismdisposed towards rear wheel 322 and/or a rear of micro-mobility fleetvehicle 410). Steps 702, 703, and 704 may generally be reversed toremove modular battery assembly 724 from subframe assembly 762.

FIG. 7B presents an exploded view of modular battery assembly 724 andsubframe assembly 762 corresponding to step 702 of FIG. 7A. In FIG. 7B,modular battery assembly 724 includes features similar to thosedescribed with respect to FIGS. 5A-B, but with the addition of archedfloorboard panel 770 with integrated ergonomic handle 717, insulatorpanels 721 and 722, and pawl 710 and pawl retention clip 711 of batteryassembly enclosure 510. Insulator panels 721 and 722 may be formed froma ceramic material able to withstand relatively high temperaturesassociated with battery cell blowout/rupture, so as to protect a riderand/or micro-mobility fleet vehicle 410 from damage in the event of suchrupture. Pawl 710 may be implemented as a latch or other componentcoupled to battery assembly enclosure 510 via pawl retention clip 711and be configured to engage with tail assembly retention mechanism 764,where tail assembly retention mechanism 764 may be implemented as anelectromechanical locking mechanism configured to lock modular batteryassembly 724 in subframe assembly 762 until a fleet servicer provides anunlock code or signal to cockpit assembly 312, for example, or uses aproprietary mechanical tool to disengage tail assembly retentionmechanism 764, release pawl 710, and pivot modular battery assembly 724out of subframe assembly 762. Arched floorboard panel 770 may be formedfrom an impact modified plastic resin, for example, and may beconfigured to provide a floorboard surface for micro-mobility fleetvehicle 410. In various embodiments, arched floorboard panel 770 mayform a structural component of micro-mobility fleet vehicle 410 and beconfigured to distribute a step weight of a rider of micro-mobilityfleet vehicle 410 along subframe assembly 762 and/or tubular framemembers 460 and 461, as described herein more fully with respect toFIGS. 9A-B.

Also shown in FIG. 7B is subframe assembly 762 including hinged assemblyretention mechanism 763. For example, hinged assembly retentionmechanism 763 may include hinge guide 790, subframe assembly electricalinterface 725 configured to mate with battery assembly electricalinterface 525, torsion springs 791, pivot shaft 792, and pivot cylinder793, which may be configured to receive and/or mate with batteryassembly retention interface 512 of modular battery assembly 724 andpivot about pivot shaft 792 to place modular battery assembly 724 withinsubframe assembly 762, for example, and to allow pawl 910 to engage withtail assembly retention mechanism 764. In some embodiments, subframeassembly 762 may include a wiring channel configured to route power bus425 from subframe assembly electrical interface 725 to motor controller420, as described herein.

FIG. 7C presents various views of modular battery assembly 724 engagedwith hinged assembly retention mechanism 763 of subframe assembly 762,as shown in step 704 of FIG. 7A. In FIG. 7C, side view 704-1 shows anassembled hinged assembly retention mechanism 763 including hinge guide790, torsion springs 791, and pivot shaft 792 mechanically couplingassembly retention interface 512 of modular battery assembly 724 tohinged assembly retention mechanism 763 of subframe assembly 762, witharched floorboard panel 770 oriented towards a front of micro-mobilityfleet vehicle 410. Front left view 704-2 shows a different perspectiveof the elements identified in view 704-1. Partial wireframe side view704-3 battery assembly electrical interface 525 mated with subframeassembly electrical interface while assembly retention interface 512 ofmodular battery assembly 724 is coupled to hinged assembly retentionmechanism 763 of subframe assembly 762.

FIG. 7D presents various internal views of modular battery assembly 724locked within subframe assembly 762, as shown in step 706 of FIG. 7A. InFIG. 7D, cross section view 706-1 shows power bus 425 routed throughwiring channel 795 of subframe assembly 762 to motor controller 420mounted to a rear external surface of subframe assembly 762.Orthographic view 706-2 shows modular battery assembly 724 securedwithin subframe assembly 762 by assembly retention mechanism 764 withtension being applied by hinged assembly retention mechanism 763.Orthographic partial wireframe view 706-3 shows power bus 425 routedfrom subframe assembly electrical interface 725 through subframeassembly 762 to motor controller 420 mounted to a rear external surfaceof subframe assembly 762.

FIG. 7E presents various internal views of modular battery assembly 724locked within subframe assembly 762, as shown in step 706 of FIG. 7A. InFIG. 7E, close cross section view 706-4 shows pawl 710 of batteryassembly enclosure 510 engaged with locking cam 712 of assemblyretention mechanism 764. Top down cross section view 706-5 shows ageneral arrangement of elements of modular battery assembly 724 lockedwithin subframe assembly 762. For example, in the process of pivotingmodular battery assembly 724 into subframe assembly 762, pawl 710 maybrush over a rounded slip portion of locking cam 712 and latch into alocking surface of locking cam 712, where pawl retention clip 711 ofbattery assembly enclosure 510 includes a spring configured to allowpawl 710 to collapse against battery assembly enclosure 510 when brushedby the rounded slip portion of locking cam 712 as modular batteryassembly 724 is lowered into subframe assembly 762 and to eject pawl 710to engage and latch into a locking surface of locking cam 712 oncemodular battery assembly 724 is seated within subframe assembly 762. Invarious embodiments, assembly retention mechanism 764 may include a wormgear coupled to locking cam 712 and an electromechanical actuator (e.g.,controlled by one or more of controller 112, battery management system442) configured to rotate the worm gear to rotate the locking surface oflocking cam 712 away from pawl 710 and release pawl 710 and/or modularbattery assembly 724 from subframe assembly 762. In various embodiments,because hinged assembly retention mechanism 763 is spring tensionedagainst lowering modular battery assembly 724 into subframe assembly762, release of pawl 710 may cause modular battery assembly 724 toautomatically pivot out of subframe assembly 762.

FIGS. 8A-D illustrate various aspects of a modular battery assembly 824for a micro-mobility fleet vehicle (e.g., micro-mobility fleet vehicle410) in accordance with embodiments of the disclosure. In particular,FIG. 8A shows three steps 802, 804, and 806 for installing modularbattery assembly 824 into a subframe assembly 862 implemented as asubframe case coupled between tubular frame members 460 and 461 andincluding a push latch head assembly retention mechanism 863 (e.g., apush latch assembly retention mechanism disposed towards head tube 321and/or a front of micro-mobility fleet vehicle 410) and a slide levertail assembly retention mechanism 864 (e.g., a slide lever assemblyretention mechanism disposed towards rear tire 322 and/or a rear ofmicro-mobility fleet vehicle 410). In the embodiment shown in FIG. 8A,subframe assembly 862 includes a floorpan panel 874 providing a floorpanfor micro-mobility fleet vehicle 410 configured to protect modularbattery assembly 824 from road debris.

In step 802, a fleet servicer technician may use battery assembly handle817 to position modular battery assembly 824 in subframe assembly 862with battery assembly retention interface 812 (e.g., a slide leverfeature) in contact and able to slide along a bottom surface of subframeassembly 862, such that arched floorboard panel 870 is facingsubstantially towards a rear of micro-mobility fleet vehicle 410 and/oraway from subframe assembly 862. In step 804, battery assembly retentioninterface 812 of modular battery assembly 824 is slid along a bottomsurface of subframe assembly 862 towards slide lever tail assemblyretention mechanism 864 to at least partially engage with and form afulcrum at slide lever tail assembly retention mechanism 864, andbattery assembly retention interface 810 (e.g., a recessed latchreceptacle which may be integrated with battery assembly electricinterface 825) is lowered towards subframe assembly 862 and/or kickstand884.

In step 806, modular battery assembly 824 is levered into subframeassembly 862 via a fulcrum formed by battery assembly retentioninterface 812 and slide lever tail assembly retention mechanism 864 andsecured in place by push latch head assembly retention mechanism 863. Inalternative embodiments, a similar series of steps may be used toinstall modular battery assembly 824 into a subframe assemblyimplemented as a subframe case coupled between tubular frame members 460and 461 and including a push latch tail assembly retention mechanism anda slide lever head assembly retention mechanism. Steps 802, 803, and 804may generally be reversed to remove modular battery assembly 824 fromsubframe assembly 862.

FIG. 8B presents various views of battery assembly retention interface812 (e.g., a slide lever feature) in contact and sliding along a bottomsurface of subframe assembly 862 towards slide lever assembly retentionmechanism 864 as modular battery assembly 824 is rotated and batteryassembly retention interface 810 (e.g., a recessed latch receptacle) islowered towards push latch assembly retention mechanism 863, as shown instep 802 of FIG. 8A. In FIG. 8B, orthographic view 802-1 shows batteryassembly retention interface 812 implemented with a rounded radius tofacilitate natural and unhindered rotation and sliding of batteryassembly retention interface 812 towards slide lever assembly retentionmechanism 864. Slide lever assembly retention mechanism 864 may includeleaf spring 867 configured to protect battery assembly retentioninterface 812 from hard contact with slide lever assembly retentionmechanism 864 and to provide tension against tolerance slack in thesizing of the various components. Push latch assembly retentionmechanism 863 may include push latch feature 865 configured to mate withbattery assembly retention interface 810 and/or battery assemblyelectrical interface 825, for example, and may include leaf spring 866configured to protect battery assembly retention interface 810 from hardcontact with push latch assembly retention mechanism 863 and to providetension against latching battery assembly retention interface 810 topush latch assembly retention mechanism 863. Close orthographic view802-2 shows battery assembly retention interface 812 approaching slidelever assembly retention mechanism 864.

FIG. 8C presents various views of battery assembly retention interface812 engaging with slide lever assembly retention mechanism 864, as shownin step 804 of FIG. 8A. In FIG. 8C, orthographic view 804-1 showsbattery assembly retention interface 812 engaged with and creating afulcrum at slide lever assembly retention mechanism 864, which allowsmodular battery assembly 824 to be levered down into subframe assembly862 such that battery assembly retention interface 810 is properlyaligned with push latch assembly retention mechanism 863. For example,as shown in close view 864-1 of slide lever assembly retention mechanism864, slide lever assembly retention mechanism 864 may include a backstopmember 890 forming a backstop recess 891 configured to receive batteryassembly retention interface 812 and fulcrum guide 892 configured toform a lever fulcrum with battery assembly retention interface 812 thatis tensioned, at least in part, by leaf spring 862 (e.g., as shown inwire frame view 864-2).

FIG. 8D presents various views of modular battery assembly 824 beinglevered into subframe assembly 862 to engage battery assembly retentioninterface 810 with push latch assembly retention mechanism 863, as shownin step 806 of FIG. 8A. In FIG. 8D, orthographic view 806-1 showsmodular battery assembly 824 being levered into subframe assembly 862 toposition battery assembly retention interface 810 over push latchassembly retention mechanism 863. As shown in FIG. 8D, push latchassembly retention mechanism 863 may include push latch feature 865configured to mate with battery assembly retention interface 810 and/orbattery assembly electrical interface 825, for example, and may includeleaf spring 866 configured to protect battery assembly retentioninterface 810 from hard contact with push latch assembly retentionmechanism 863 and to provide tension against latching battery assemblyretention interface 810 to push latch feature 865 of push latch assemblyretention mechanism 863. Close cross section view 806-2 shows batteryassembly retention interface 810 just above push latch feature 865, andclose cross section view 806-2 shows battery assembly retentioninterface 810 mated with and latched to push latch feature 865 of pushlatch assembly retention mechanism 863 and tensioned by leaf spring 866.

In various embodiments, push latch assembly retention mechanism 863 mayinclude a worm gear coupled to push latch feature 865 and anelectromechanical actuator (e.g., controlled by one or more ofcontroller 112, battery management system 442) configured to rotate theworm gear to rotate a locking surface or slot of push latch feature 865and release battery assembly retention interface 810 and/or modularbattery assembly 824 from subframe assembly 862. In various embodiments,because push latch assembly retention mechanism 863 is spring tensionedagainst lowering modular battery assembly 824 into subframe assembly862, release of battery assembly retention interface 810 may causemodular battery assembly 824 to automatically lever out of subframeassembly 862.

FIGS. 9A-B illustrate various aspects of a modular battery assembly 924for a micro-mobility fleet vehicle (e.g., micro-mobility fleet vehicle410) in accordance with embodiments of the disclosure. In the embodimentshown in FIG. 9A, modular battery assembly 924 may be secured tosubframe assembly 962 via slip pin head assembly retention mechanism 963and lock pin tail assembly retention mechanism 964. For example, slippin head assembly retention mechanism 963 may include slip pin tabs 967(e.g., left and right slip pin tabs) configured to receive respectiveslip pins/battery assembly retention interfaces 968 as modular batteryassembly 924 is inserted into subframe assembly 962 generally from aread of micro-mobility fleet vehicle 410. Lock pin tail assemblyretention mechanism 964 may include lock pin tabs 965 configured toreceive respective lock pins/battery assembly retention interfaces 966as modular battery assembly 924 is first slipped into slip pin tabs 967(e.g., forming a fulcrum at slip pin tabs 967) and then levered downinto subframe assembly 962 to engage lock pin tabs 965 with lock pins966. In some embodiments, modular battery assembly 924 may includedeformable preloading member 973 configured to tension against subframeassembly 962 to dissipate vibrations during operation and deform toallow for slip fit clearance for battery replacement. In variousembodiments, subframe assembly 962 includes a floorpan panel 974providing a floorpan for micro-mobility fleet vehicle 410 configured toprotect modular battery assembly 924 from road debris.

As shown in FIG. 9A, modular battery assembly 924 may include archedfloorboard panel 970 configured both to protect modular battery assembly924 and to form a structural member of micro-mobility fleet vehicle 410configured to distribute a step weight of a rider (e.g., weight appliedto a top surface of arched floorboard panel 970 by a rider operatingmicro-mobility fleet vehicle 410) to subframe assembly 962 and/ortubular frame members 460 and 461. For example, arched floorboard panel970 may be formed according to a tensioned arch extending laterallybetween tubular frame members 460 and 461 so as to distribute the stepweight laterally towards tubular frame members 460 and 461, for example,or into subframe assembly 974 (e.g., which may be welded to tubularframe members 460 and 461). Moreover, such tensioned arch may be shapedto form an air gap between arched floorboard panel and enclosure lid918, for example, to reduce thermal loading caused by sunlight. In someembodiments, arched floorboard panel 970 may include head flange 971disposed towards a front of micro-mobility fleet vehicle 410 and tailflange 972 disposed towards a rear of micro-mobility fleet vehicle 410,where head flange 971 and tail flange 972 are shaped to form waterresistant seals against water ingress into subframe assembly 962. Invarious embodiments, arched floorboard panel 970 may be tensioned and/orsupported by slip pin tabs 967 and lock pin tabs 965 at left and righttensioning points 984 and 985.

For example, as shown in FIG. 9B, lateral cross section view 924 aillustrates that arched floorboard panel 970 may include arch supportguides 969 configured to receive slip pin tabs 967 and lock pin tabs 965and provide lateral compression of, and vertical support for, archedfloorboard panel 970, which act together to retain the lateral archshape of arched floorboard panel 970. In addition, arched floorboardpanel 970 may include overhangs 980 and 981, for example, which may beconfigured to tension against left and right tubular frame members 460and 461 to provide lateral compression of arched floorboard panel 970.In some embodiments, modular battery assembly 924 may be configured tocontact subframe assembly 962 at case perimeters 982 and 983 (e.g.,disposed below an enclosure lip of a battery assembly enclosure ofmodular battery assembly 924) and provide lateral tensioning and/orvertical support for arched floorboard panel 970 through such contact.Lateral cross section view 924 a and longitudinal cross section view 924b illustrate how features of arched floorboard panel 970, including headflange 971 and tail flange 972 are shaped to form water resistant sealsagainst water ingress into subframe assembly 962, such that waterstreams 988 and 989 flow around electrical components of propulsionsystem 122, for example, and/or water streams 986 and 987 flow outsidesubframe assembly 962 even if they do not flow outside tubular framemembers 460/461.

FIG. 10 illustrates a flow diagram of a process 1000 to replace (e.g.,remove and/or install) a modular battery assembly for a micro-mobilityfleet vehicle (e.g., micro-mobility fleet vehicle 410) in accordancewith an embodiment of the disclosure. It should be appreciated that anystep, sub-step, sub-process, or block of process 1000 may be performedin an order or arrangement different from the embodiments illustrated byFIG. 10 . For example, in other embodiments, one or more blocks may beomitted from or added to the process. Furthermore, block inputs, blockoutputs, various sensor signals, sensor information, calibrationparameters, and/or other operational parameters may be stored to one ormore memories prior to moving to a following portion of a correspondingprocess. Although process 1000 is described with reference to systems,processes, control loops, and images described in reference to FIGS.1-9E, process 1000 may be performed by other systems different fromthose systems, processes, control loops, and images and including adifferent selection of electronic devices, sensors, assemblies, mobilestructures, and/or mobile structure attributes, for example.

In block 1002, a charge level of a modular battery assembly is reported.For example, controller 112 of micro-mobility fleet vehicle 410 may beconfigured to report a charge level of modular battery assembly 424,other battery monitoring data, and/or other vehicle status data tomanagement system 240 via one or more of fleet data links 436. In someembodiments, controller 112 may be configured to monitor such chargelevel and report the charge level upon detecting it has fallen below apredetermined minimum charge level. In other embodiments, controller 112may be configured to receive periodic vehicle status requests frommanagement system 240 and report the charge level as part of a vehiclestatus report provided to management system 240. Such reporting may insome embodiments include a variety of contextual status information,such as location, time of day, and declined rentals (e.g., due to toolow a charge level for a requested trip), which may be used to helpdetermine whether to replace modular battery assembly 424 with a chargedmodular battery assembly.

In block 1004, a release request for a modular battery is received. Forexample, controller 112 of micro-mobility fleet vehicle 410 may beconfigured to receive a release requests (e.g., as fleet status data)from a user device of a fleet service technician, from management system240, and/or from another authorized entity, including in some instancesa rider of micro-mobility fleet vehicle 410. Upon receiving such releaserequest, controller 112 may proceed direction to block 1006, forexample, or may notice various elements of systems 100 or 400 thatmodular battery assembly 424 will be released. Upon such notice, batterymanagement system 442 may be configured to store related vehicle statusinformation to memory 447. In alternative embodiments, controller 112may be configured to provide a snapshot of all available vehicle statusinformation to battery management system 442 of modular battery assembly424, and battery management system 442 may be configured to store suchinformation and notice controller 112 upon completion. Controller 112may be configured to delay release until such notice is received.

In block 1006, a modular battery assembly is released. For example,controller 112 of micro-mobility fleet vehicle 410 may be configured tocontrol an assembly retention mechanism (e.g., a lock pin tab, lockingcam, and/or push latch assembly retention mechanism) to release modularbattery assembly 424 from subframe assembly 462, as described herein.Upon such release, battery management system 442 may be configured todetect such release and/or store related vehicle status information tomemory 447.

In block 1008, installation of a modular battery assembly is detected.For example, battery management system 442 of modular battery assembly424 may be configured to detect proper insertion/installation of modularbattery assembly 424 into subframe assembly 462 of micro-mobility fleetvehicle 410. In some embodiments, battery management system 442 may beconfigured to report such detection to controller 112, such as aftercontroller 112 and/or various data buses are powered by modular batteryassembly 424.

In block 1010, a charge level of a modular battery assembly is reported.For example, similar to block 1002, controller 112 of micro-mobilityfleet vehicle 410 may be configured to report a charge level of modularbattery assembly 424, other battery monitoring data, and/or othervehicle status data to management system 240 via one or more of fleetdata links 436. In some embodiments, controller 112 may be configured toreport such charge level upon detecting the modular battery assembly hasbeen replaced. In other embodiments, controller 112 may be configured toreceive periodic vehicle status requests from management system 240 andreport the charge level as part of a vehicle status report provided tomanagement system 240. Such reporting may in some embodiments include avariety of contextual status information, such as location, time of day,and declined rentals (e.g., due to too low a charge level for arequested trip), as described herein.

Embodiments of the present disclosure can thus provide a reliable androbust methodology to reduce burdens associated with servicingmicro-mobility fleet vehicles provided for hire by a transportationservices provider employing a dynamic transportation matching system tolink fleet vehicles to requestors/riders of micro-mobility fleetvehicles, as described herein.

Where applicable, various embodiments provided by the present disclosurecan be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein can be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the spirit of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein can be separated into sub-components comprising software,hardware, or both without departing from the spirit of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components can be implemented as hardware components, andvice-versa.

Software in accordance with the present disclosure, such asnon-transitory instructions, program code, and/or data, can be stored onone or more non-transitory machine readable mediums. It is alsocontemplated that software identified herein can be implemented usingone or more general purpose or specific purpose computers and/orcomputer systems, networked and/or otherwise. Where applicable, theordering of various steps described herein can be changed, combined intocomposite steps, and/or separated into sub-steps to provide featuresdescribed herein.

Embodiments described above illustrate but do not limit the invention.It should also be understood that numerous modifications and variationsare possible in accordance with the principles of the invention.Accordingly, the scope of the invention is defined only by the followingclaims.

What is claimed is:
 1. A modular battery assembly for a micro-mobilityfleet vehicle, the modular battery assembly comprising: a batteryassembly enclosure comprising an enclosure cavity and a battery assemblyelectrical interface; a battery cell assembly comprising a plurality ofbattery cells disposed within the enclosure cavity and electricallycoupled to the battery assembly electrical interface of the batteryassembly enclosure; and an enclosure lid mounted to the battery assemblyenclosure and configured to seal the enclosure cavity, wherein thebattery cell assembly comprises: a honeycomb battery cell holdercomprising a hexagonally packed array of hexagonal prism shaped batterycell cavities extending along a length of each one of the plurality ofbattery cells enclosed therein; a collector board disposed atop thehoneycomb battery cell holder and including an array of battery cellaccess wells; and a plurality of wire bond pads interposed between pairsof battery cell access wells of the array of battery cell access wells,wherein the plurality of wire bond pads is configured to wire bond eachpositive terminal and negative terminal of the plurality of batterycells.
 2. The modular battery assembly of claim 1, wherein: each batterycell cavity comprises a bottom access hole configured to receive athermal adhesive disk; and each thermal adhesive disk is configured tothermally and mechanically couple a corresponding battery cell to abottom surface of the enclosure cavity.
 3. The modular battery assemblyof claim 1, wherein: a hexagonal perimeter of each battery cell cavityforms six cell-length air gaps configured to thermally isolate adjacentbattery cells from each other and provide space for venting in the eventof a thermal overrun of an individual battery cell; and each batterycell cavity comprises one or more crush ribs disposed along a length ofan interior surface of the battery cell cavity and configured tophysically secure a corresponding battery cell.
 4. The modular batteryassembly of claim 1, wherein: each battery cell access well comprises akeyhole shaped battery cell access well comprising a disk portionconfigured to provide a physical access or a wire bonding access to acell cap of a corresponding battery cell and a notch portion.
 5. Themodular battery assembly of claim 1, further comprising a batterymanagement system disposed within the battery assembly enclosure andcoupled to the honeycomb battery cell holder, wherein: the enclosurecavity comprises a waterproof pressure relief patch configured to allowpressurized air or contaminates to exit the enclosure cavity.
 6. Themodular battery assembly of claim 1, wherein: the battery assemblyenclosure comprises an assembly retention interface configured tophysically secure the battery assembly enclosure to a subframe assemblymounted to the micro-mobility fleet vehicle; and the assembly retentioninterface comprises a slide lever feature configured to engage and forma fulcrum with a slide lever assembly retention mechanism of thesubframe enclosure.
 7. The modular battery assembly of claim 1, wherein:the battery assembly enclosure comprises an assembly retention interfaceconfigured to physically secure the battery assembly enclosure to asubframe assembly mounted to the micro-mobility fleet vehicle; and theassembly retention interface comprises a recessed latch receptacleconfigured to engage with a push latch assembly retention mechanism ofthe subframe enclosure.
 8. A micro-mobility fleet vehicle, comprising: asubframe assembly mounted to the micro-mobility fleet vehicle; and amodular battery assembly comprising: a battery assembly enclosurecomprising an enclosure cavity and a battery assembly electricalinterface; a battery cell assembly comprising a plurality of batterycells disposed within the enclosure cavity and electrically coupled tothe battery assembly electrical interface; and an enclosure lid mountedto the battery assembly enclosure and configured to seal the enclosurecavity and to prevent ambient moisture from entering the batteryassembly enclosure, wherein the battery cell assembly comprises: ahoneycomb battery cell holder comprising a hexagonally packed array ofhexagonal prism shaped battery cell cavities extending along a length ofeach one of the plurality of battery cells enclosed therein; a collectorboard disposed atop the honeycomb battery cell holder and including anarray of battery cell access wells; and a plurality of wire bond padsinterposed between pairs of battery cell access wells of the array ofbattery cell access wells, wherein the plurality of wire bond pads isconfigured to wire bond each positive terminal and negative terminal ofthe plurality of battery cells.
 9. The micro-mobility fleet vehicle ofclaim 8, wherein: each battery cell cavity comprises a bottom accesshole configured to receive a thermal adhesive disk; and each thermaladhesive disk is configured to thermally and mechanically couple acorresponding battery cell to a bottom surface of the enclosure cavity.10. The micro-mobility fleet vehicle of claim 8, wherein: a hexagonalperimeter of each battery cell cavity forms six cell-length air gapsconfigured to thermally isolate adjacent battery cells from each otherand provide space for venting in the event of a thermal overrun of anindividual cell; and each battery cell cavity comprises one or morecrush ribs disposed along a length of an interior surface of the batterycell cavity and configured to physically secure a corresponding batterycell in place.
 11. The micro-mobility fleet vehicle of claim 8, furthercomprising a battery management system disposed within the batteryassembly enclosure and coupled to the honeycomb battery cell holder,wherein: the enclosure cavity comprises a waterproof pressure reliefpatch configured to allow pressurized air or contaminates to exit theenclosure cavity.
 12. The micro-mobility fleet vehicle of claim 8,wherein: the battery assembly enclosure comprises an assembly retentioninterface configured to physically secure the battery assembly enclosureto the subframe assembly; and the assembly retention interface comprisesa slide lever feature configured to engage and form a fulcrum with aslide lever assembly retention mechanism of the subframe enclosure. 13.The micro-mobility fleet vehicle of claim 8, wherein: the batteryassembly enclosure comprises an assembly retention interface configuredto physically secure the battery assembly enclosure to the subframeassembly; and the assembly retention interface comprises a recessedlatch receptacle configured to engage with a push latch assemblyretention mechanism of the subframe enclosure.
 14. The micro-mobilityfleet vehicle of claim 8, wherein the array of battery cell access wellsand the plurality of wire bond pads are exposed at a top surface of thecollector board.
 15. The micro-mobility fleet vehicle of claim 8,wherein: the modular battery assembly is physically secured to thesubframe assembly by an assembly retention interface of the batteryassembly enclosure; and each battery cell access well comprises akeyhole shaped battery cell access well comprising a disk portionconfigured to provide a physical access or a wire bonding access to acell cap of a corresponding battery cell and a notch portion.
 16. Amethod, comprising: receiving a release request for a first modularbattery assembly coupled to a micro-mobility fleet vehicle, wherein thefirst modular battery assembly comprises: a battery assembly enclosurecomprising an enclosure cavity and a battery assembly electricalinterface; a battery cell assembly comprising a plurality of batterycells disposed within the enclosure cavity and electrically coupled tothe battery assembly electrical interface of the battery assemblyenclosure; and an enclosure lid mounted to the battery assemblyenclosure and configured to seal the enclosure cavity, wherein thebattery cell assembly comprises: a honeycomb battery cell holdercomprising a hexagonally packed array of hexagonal prism shaped batterycell cavities extending along a full length of each one of the pluralityof battery cells enclosed therein; a collector board disposed atop thehoneycomb battery cell holder and including an array of battery cellaccess wells; and a plurality of wire bond pads interposed between pairsof battery cell access wells of the array of battery cell access wells,wherein the plurality of wire bond pads is configured to wire bond eachpositive terminal and negative terminal of the plurality of batterycells; releasing the first modular battery assembly; and detecting aninstallation of a second modular battery assembly.
 17. The method ofclaim 16, further comprising: reporting a charge level of the firstmodular battery assembly prior to receiving the release request for thefirst modular battery assembly; and reporting a charge level of thesecond modular battery assembly after detecting the installation of thesecond modular battery assembly.
 18. The method of claim 16, wherein thefirst modular battery assembly comprises a data storage deviceconfigured to receive vehicle status data over a data bus of themicro-mobility fleet vehicle, the method further comprising: requestingvehicle status data from a controller of the micro-mobility fleetvehicle after receiving the release request; and storing the vehiclestatus data to the data storage device prior to releasing the firstmodular battery assembly.
 19. The method of claim 16, wherein: eachbattery cell cavity comprises a bottom access hole configured to receivea thermal adhesive disk; and each thermal adhesive disk is configured tothermally and mechanically couple a corresponding battery cell to abottom surface of the enclosure cavity.
 20. The method of claim 16,wherein: each battery cell cavity comprises one or more crush ribsdisposed along a length of an interior surface of the battery cellcavity and configured to physically secure a corresponding battery cell.